Closed the-codetrane closed 3 years ago
It would appear that these breaking changes are what's causing the issue:
before_prepare
was changed to #ready?
validate_* hooks
were replaced with a single #authorized?
method#ready?
and #authorized?
may halt flow and/or return data #1736, #1737.scope_items(items, ctx)
hook for filtering lists#default_graphql_name
for overriding default logic #1729#add_argument
for building schemas #1732urlsafe_decode64
to future-proof for urlsafe cursors #1748@the-codetrane - This gem doesn't unless we downgrade to an older version of graphql (currently at v1.9.7)?
@ACPK that would appear to be the case. These were the breaking changes I found that interfered with the gem. Now, this may have been resolved with v. 1.9.7. I was working with 1.9.3 at the time.
Closed per new releases.
I have been trying to use this version of
graphiql-rails
withgraphql
version 1.9.3, which gave me the below response. When I ported back to 1.18.0, the proper response came through. I apologize that I can't make a PR myself to resolve this at the moment, since I'm a total n00b to GraphQL, but I wanted to make you aware for your next release.Big fan of the tool, so thank you for the work y'all have done!
Michael
Mutation Type
Mutation
GraphQL mutation
Return value