Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Types that lack an "isDeprecated" are included in the deprecation list by default
See original GitHub issueAs of v1 the isDeprecated field defaults to true if it is not found or defined, which can be seen here. This behavior changed from the v0.x behavior where fields without an isDeprecated field are simply being ignored, which is also what you’d expect.
The issue we are running into is that our graphql server (graphql-dotnet) omits the isDeprecated field for input type fields that are not deprecated, which is now causing the “Show deprecated fields” button to pop up and contain all fields when clicked.
Was this change done deliberately, and would you be ok with a PR that reverts this to the v0.x behavior?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
can I make a PR for this @acao?
we have to restructure the repo a bit before we can make the next release to graphiql 1.x, so, sometime in the coming weeks when i get a chance! stay tuned!