Make GraphiQLProvider component's "inputValueDeprecation" property configurable
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 625
- Avg merge
- 5h 23m
- Merged PRs (30d)
- 24
Description
### Feature description
Make [the inputValueDeprecation property of the GraphiQLProvider component](https://github.com/graphile/crystal/blob/main/grafast/ruru-components/src/ruru.tsx#L73) configurable.
### Motivating example
Some graphql schemas, such as [the one included in the Hasura GraphQL Engine](https://github.com/hasura/graphql-engine/blob/master/server/src-lib/Hasura/GraphQL/Schema/Introspect.hs#L547), don't support an **includeDeprecated** argument at the IntrospectionQuery's fields' types' args level, and t[he graphql npm library support its configurable inclusion](https://github.com/graphql/graphql-js/blob/main/src/utilities/getIntrospectionQuery.ts#L107) via the **inputValueDeprecation**, which is [passed](https://github.com/graphql/graphiql/blob/cd5f72390578dd37e72c2b40f1c498efa61277ba/packages/graphiql-react/src/schema.tsx#L391) by [the GraphiQLProvider component](https://github.com/graphql/graphiql/blob/main/packages/graphiql-react/src/provider.tsx#L33) to the IntrospectionQuery retrieval method, so the ruru integration of the component should include configurability of the GraphiQLProvider's **inputValueDeprecation** property.
### Breaking changes
### Supporting development
I [tick all that apply]:
- [ ] am interested in building this feature myself
- [ ] am interested in collaborating on building this feature
- [ ] am willing to help testing this feature before it's released
- [ ] am willing to write a test-driven test suite for this feature (before it exists)
- [ ] am a [Graphile sponsor](https://www.graphile.org/sponsor/) ❤️
- [ ] have an active [support or consultancy contract](https://www.graphile.org/support/) with Graphile
Contributor guide
Assessment
This issue has not been assessed yet.