graphql / graphql/graphql.github.io
Explain errors as data
Open
💄 Enhancement
- Dominant language
- TypeScript
- Stars
- 889
- Forks
- 1.5k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 21
Description
As suggested in https://github.com/graphql/graphql-js/issues/560
Sometimes errors are totally expected and deserve to be represented as data in an API. This is worth a best practices post
Contributor guide
Research direction
Start by reading this issue and the referenced graphql/graphql-js#560 discussion to understand the proposed guidance. Identify the intended audience, examples, and location for a best-practices post; done should mean the agreed post is written and published in the website's documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100