-
Notifications
You must be signed in to change notification settings - Fork 1.4k
"Legacy .graphql_definition
objects are deprecated and will be removed in GraphQL-Ruby 2.0" on a definition without graphql_definition
#4947
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.
All reactions
-
Sorry for not getting back to you earlier. In fact, it doesn't; I still get the previous warning, but now also
Previously it was only And in addition, the app fails to start:
I thought maybe I needed to update the |
Beta Was this translation helpful? Give feedback.
-
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