You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If preserving the current behaviour is desireable for backwards compatibility, perhaps a separate "preferGet" type flag could be used, which uses POST for mutation and GET for all else.
The text was updated successfully, but these errors were encountered:
If the fetcher is configured to use GET, the result is that even mutations are issued as GETs.
From the closest thing to a spec in this area (https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md):
See https://github.com/apollographql/apollo-client/blob/287aa465d56fea7d2171533921e73b78caac26a7/src/link/http/createHttpLink.ts#L99-L104 for behaviour that ignores a request for a GET containing a mutation.
If preserving the current behaviour is desireable for backwards compatibility, perhaps a separate "preferGet" type flag could be used, which uses POST for mutation and GET for all else.
The text was updated successfully, but these errors were encountered: