Consider integrating or referencing GraphQL multipart spec
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- graphql
- Domain
- api
Research direction
Start by reading the current GraphQL over HTTP working draft and the linked graphql multipart request spec. Determine whether the intended outcome is integration or a reference, then define the relevant specification changes and acceptance criteria. Done means the chosen approach is documented in the specification.
Written by the indexing model from the issue text.
Description
When it comes to sending large scalars over HTTP, @jaydenseric's graphql multipart spec is the de facto standard at this point, being supported by many languages and tools, including Apollo's ecosystem.
There is probably value to either integrating or referencing his spec here.
- Dominant language
- JavaScript
- Stars
- 428
- Forks
- 70
- Avg merge
- 11m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 graphql/graphql-over-http
-
Difficulty 3/5 Half a day Newbie friendliness 25/100
graphql/graphql-over-http#446 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphql/graphql-over-http#415 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphql/graphql-over-http#392 · 4 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
graphql/graphql-over-http#242 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
graphql/graphql-over-http#216 · 15 comments · 1 reaction ·
All issues in graphql/graphql-over-http
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openlayers/openlayers#17736 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#4326 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Mintplex-Labs/anything-llm#7133 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day