"Legacy .graphql_definition
objects are deprecated and will be removed in GraphQL-Ruby 2.0" on a definition without graphql_definition
#4947
Unanswered
alexeyr-ci
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hey, thanks for reporting this. I think this is triggered by some old code in I just released GraphQL-Pro 1.27.5 without this call (it was unused) -- does updating to that version work for you? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have this directive definition:
but when the app starts, I see
Looking at our code,
graphql_definition
is only called at the end of the schema class:Should it be replaced by
in the beginning of the class, as in the last comment on that issue #1505 (comment)? Or just not worry about it for now?
I'm just a bit confused why a directive triggers this warning but all the other definitions we already have don't.
Beta Was this translation helpful? Give feedback.
All reactions