graphql-python / graphql-python/graphql-core-legacy
Quiver source
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 371
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
It seems like a lot of people (us included) will not be able to move off of core-legacy any time soon, and enjoy the fruits of native async/await. Given that Quiver seems dead, is there any chance that @syrusakbary will open source it so that we can include it as a backend and improve the performance of the core legacy library?
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
The issue names Quiver and the core-legacy backend but does not identify a repository file, test, or entry point. First verify whether Quiver can be open sourced and define the integration scope; done would require available Quiver source and an agreed backend implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100