ChilliCream / ChilliCream/graphql-platform
Spec: Track Introduce Strict and Legacy All Variable Usages Are Allowed
Open
Nobody has claimed this yet.
⚖️ spec
🌶️ hot chocolate
Area: Type System
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
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 graphql/graphql-spec pull request #1059, the only implementation reference provided; this issue names no repository file, test, or entry point. Compare the proposal with the current variable-usage behavior, identify affected tests, and define completion criteria for strict and legacy handling before coding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100