Deprecation of Operation.operationName #1267
-
Hey, I'm checking out this library for the first time and I'm currently using React-Native + Urql in my project.
So I really don't know where to start debugging this to begin with since I'm pretty much just querying in the most simple way
and this is my query:
and these are the versions of all libraries that I'm using
Thank you all |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hiya 👋 Either way you can ignore the warning though. We're also considering to just remove it until the removal of the field, since the warning misfires on shallow copies or debug prints of operations. |
Beta Was this translation helpful? Give feedback.
-
Hey @kitten 👋
It happens exactly inside my modal where my custom hook is located at.
So I think that was my fault hehe |
Beta Was this translation helpful? Give feedback.
Hiya 👋
This is just a temporary warning as we've indeed renamed the field recently. Do you have some traces around where it's been logged? That'll usually give me some info to tell you where it's coming from.
Either way you can ignore the warning though. We're also considering to just remove it until the removal of the field, since the warning misfires on shallow copies or debug prints of operations.