leoasis / leoasis/graphql-persisted-document-loader
Fails when used with queries that include imports
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
For any queries or mutations that include imported fragments (as supported by graphql-tag/loader), the hash will not match the one generated by Apollo Server, resulting in a sha mismatch error.
Contributor guide
No contributing guide indexed for this repository
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 loader.js implementation referenced in the issue and trace how imported fragments are handled before the document hash is produced. Compare the generated hash with Apollo Server for queries and mutations using graphql-tag/loader imports; done means those hashes match without a sha mismatch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript
- Domain
- api, build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100