Graphql documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- graphql
- Domain
- api, documentation
Research direction
Compare the GraphQL custom queries and custom mutations sections with the Workflow of the resolvers section and the Extending API Platform documentation linked in the issue. First verify the current guidance around DTO, Processor, Provider, and resolvers, then update the documentation so the recommended approach is clear and the resolver approach is presented as an alternative. Done means the sections consistently reflect the agreed best practice.
Written by the indexing model from the issue text.
Description
The Graphql support part of the documentation recommends to use resolvers for custom queries and mutations.
At the same time, the beginning of the Workflow of the resolvers part recommends to see Extending API Platform documentation for more information.
The last part seems more relevant to me and more up-to-date with nowadays best pratices. I'm willing to rewrite this part using DTO, Processor and Provider to follow API Platform docs, and let the Resolver part as an alternate way to do (but not the first one). Before that, I would like to be sure if it the way to go. Can someone confirm ?
Thanks
- Dominant language
- No language data
- Stars
- 181
- Forks
- 1.1k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 24
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.
More from api-platform/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
api-platform/docs#2284 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
api-platform/docs#2318 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
api-platform/docs#2280 · 2 comments ·
-
Needs Work
Difficulty 4/5 3-5 days Newbie friendliness 35/100
api-platform/docs#2133 · 9 comments · 1 reaction ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 58/100
api-platform/docs#1450 · 2 comments ·
All issues in api-platform/docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
stratum-mining/stratum#2404 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Diaoul/subliminal#1382 ·
-
fix(errors): EHOSTUNREACH from a happy-eyeballs connect is reported as a resolver error (STAMP-80) Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
snapshot-labs/stamp#666 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GauravKarakoti/SecureFlow#1070 · 1 comment ·
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·