Team Mutations

[kevinhughes27]

part of #750

This PR adds the first mutation and hopes to establish some good patterns around Forms and Mutations for Admin Next.

Relay mutations are cool and I like the optimistic update feature that is built in. I played around with the cache to figure out how it works and I learned that mutations always pass the force option which clears the whole cache after any mutation in my current setup. This is simple and easy for now. Eventually I might add https://github.com/relay-tools/react-relay-network-modern to do some more advanced things.

I got a fragmentContainer working for the division select. This pattern is more interesting that I most recently thought (#785) because even though you have to wire it all together manually Relay seems to add some nice checks to make sure you did it right. If your fragment container isn't passed what it asked for it throws an error.

In the diff right now you can see that I had to make the mutation public to test this locally. It would work on production because of how Rails serves the app it can set the session but locally there is no way for rails to set the session. To fix this I will have to add JWT auth to the app. This is unexpected but its how most people are doing things for their frontends these days. Long term jwt will be needed for my multi client and static pages on custom domains vision. It may also let us remove devise or some devise magic eventually.

Next

• update + confirm pattern
• form to create a new Team, how will this affect code / component re-use?

Future

• Now that I sort of understand fragmentContainers I should revisit using them for Show Pages