Rethink how graphql plugins work
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
- Consider entirely removing support for python plugins (not sure if it is still possible to use them)
- Figure out which kinds of plugins we want to support
- Try to revisit dynamic_graphql API, maybe we can do some stuff that was previously impossible
- Remember adding spawn blocking when doing so
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
The issue names no files or tests; start by locating the plugin support and dynamic_graphql API in the Rust codebase. Clarify which plugin kinds remain supported, whether Python plugins can be removed, what dynamic_graphql should enable, and where spawn blocking must be added before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, python, rust
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100