Proper treatment of deprecated portions of schema

[graphql]

Proper treatment of deprecated portions of schema

[stubailo]

Related: graphql/graphql-js#389

[rewop]

I would like to contribute on this one.

If I understand this issue correctly, we could add visual cues about deprecated fields in the DocExplorer such as strikethrough text for the name, and deprecation reasons in the description.

Would this solve this issue? Or there is more?

[kdaigle]

@rewop as just another user of this library, I'd love to see the deprecation when looking through the Doc tray on the right. Super bonus points if the query itself got some treatment when using autocomplete to so a warning when using a deprecated field. 👍

[1aurabrown]

hello, I deprecated some enum values in our codebase, however I don't see an accompanying message appearing in the Docs panel when I use the deprecated enum. In our implementation, the enum is being used as an argument. I'm not familiar with the graphql code base, and I'm wondering if the change that was made to display deprecationReasons in the Docs panel does not account for enums used as an argument. like @kdaigle, I also think it would be nice if the deprecated enum values were treated with some visual indication in the autocomplete.

In the examples below, we had some enums whose values were lowercase, and I wanted to standardize them with new uppercase values, deprecating the lowercase ones.

---

no message in docs when using a deprecated enum value:

would be nice to have a strikethrough or grey color on deprecated fields:

If someone can show me around a little bit, I'm happy to PR a change.

[asiandrummer]

@1aurabrown - Probably related to #273 - we can continue this discussion there!