You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋 Thanks for the question. That does seem strange, would you mind opening a support conversation from inside Apollo Studio so we can inspect your specific situation?
Done. Thanks for the quick reply!
I'd have another quick question, is there a way to mark fields as deprecated while using introspection? I noticed that introspection removes the annotation so it gave me the feeling that the only way to deprecate fields is to submit the raw graphql schema file to Apollo Studio.
I noticed you might be trying to deprecate input type fields, which has been a long-standing issue at the GraphQL specification level: graphql/graphql-spec#805. It looks like there is some recent progress and possibly still in-flight work on this in the graphql-js package which might be relevant. graphql/graphql-js#2855 graphql/graphql-js#3048
Hi, I deprecated a field in my schema using the
@deprecated
directive and then I pushed it to Apollo Studio.Now I see it in the SDL:
It's even being displayed as deprecated in the changelog:
But then when I'm going to the
Deprecations
tab of theFields
, I'm getting:Am I missing something? Thanks in advance 🙏
The text was updated successfully, but these errors were encountered: