ChilliCream / ChilliCream/graphql-platform
Provide richer GraphQL errors when IncludeExceptionDetails is enabled
Open
Nobody has claimed this yet.
🌶️ hot chocolate
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Currently we have to limit the details we include in error messages, since attackers could fingerprint / infer details about the implementation otherwise.
It would be helpful to provide more details in certain cases though.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the IncludeExceptionDetails option and the GraphQL error-generation path. The issue names no files, tests, or concrete cases; first confirm which details are safe and what output is expected, then document the accepted behavior and its tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, graphql
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100