Graphiql: Types that lack an "isDeprecated" are included in the deprecation list by default
As 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?
pleunv
All 5 comments
woah good catch! seems this is a regression from the typescript migration
can you open a PR against 1.0.0 branch for that? thank you!
acao
on 26 Jun 2020
can I make a PR for this @acao?
harshithpabbati
on 27 Jun 2020
When will this fix be released?
kahirokunn
on 3 Sep 2020
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!
acao
on 6 Sep 2020
this was released last week in 1.0.4, forgot to update here! enjoy!
acao
on 18 Sep 2020
Related issues
songololo
路
25Comments
orta
路
10Comments
divyenduz
路
16Comments
rherrmann
路
19Comments
ElijahLynn
路
10Comments
Most helpful comment
can I make a PR for this @acao?