graphql-python / graphql-python/graphene
Explicit input instantiation escape hatch
- Lingua principale
- Python
- Stelle
- 8.2k
- Fork
- 818
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
**Is your feature request related to a problem? Please describe.**
I'm designing a stable external API that needs to wrap our existing fast-moving internal API. Sometimes, I want to call existing resolvers to do that.
However, when using deeply nested inputs with a `@property`, it's not possible to wrap that input with another (simplified) input, because I can't create an "instance" with the correct parameters on creation.
**Describe the solution you'd like**
I would like an escape hatch to instantiate inputs.
**Describe alternatives you've considered**
An inheritance-based mechanism where I could remove fields and structures from a parent might solve the problem, but I don't think it would be as clean.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
No files, tests, or entry points are named. Clarify the intended input-instantiation API, especially how deeply nested inputs and @property fields should behave, then identify the existing input construction and resolver paths to inspect. Done should include a defined escape hatch and coverage for the wrapping use case.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- graphql, python
- Ambito
- api, backend-api-design
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100