We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reads/ updates to cache often require using [fragments].(https://www.apollographql.com/docs/react/caching/cache-interaction/#readfragment). Currently the entry-point function does not allow for parsing only a fragment, this won;t conform to schema:
(graphql-query {:fragments [{:fragment/name :fragment/followFields :fragment/type :User :fragment/fields [:user/is-followed :user/followers-count]}]})
it is possible to still generate the gql fragment by passing a manually conformed map:
(fragment-str {:fragment/name :fragment/followFields :fragment/type :User :fragment/fields [[:graphql-query/field :user/is-followed] [:graphql-query/field :user/followers-count]]})
But it should be supported "natively".
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Reads/ updates to cache often require using [fragments].(https://www.apollographql.com/docs/react/caching/cache-interaction/#readfragment). Currently the entry-point function does not allow for parsing only a fragment, this won;t conform to schema:
it is possible to still generate the gql fragment by passing a manually conformed map:
But it should be supported "natively".
The text was updated successfully, but these errors were encountered: