0xPlaygrounds / 0xPlaygrounds/subgrounds

GraphQL <-> Subgrounds Query

Offen
#26 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
enhancement
Vorherrschende Sprache
Python
Sterne
73
Forks
12
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

**Is your feature request related to a problem? Please describe.**
- I'm frustrated when trying to convert existing GraphQL queries into Subgrounds
- I find it difficult to convert Subgrounds queries into clean GraphQL

**Describe the solution you'd like**
A way to convert (even if lossy) GraphQL into Subgrounds code and vice versa.

**Describe alternatives you've considered**
DMing the Playgrounds Team 😮‍💨

**Additional context**
- [GraphQL-core](https://graphql-core-3.readthedocs.io/en/latest/diffs.html#custom-middleware)
- GraphQL -> Subgrounds can be loss-less
- Subgrounds -> GraphQL will usually be lossy due to extra features we add such as pagination and synthetic fields

**Implementation checklist**
- [ ] Task 1

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

The issue is about building a converter between GraphQL queries and Subgrounds code. Start by examining the existing Subgrounds query builder and GraphQL parsing logic in the codebase. Look for modules handling GraphQL schema parsing and query generation. Understand how Subgrounds adds features like pagination and synthetic fields. A successful implementation will allow bidirectional conversion, with the Subgrounds-to-GraphQL path being lossy.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
graphql, python
Bereich
backend-api-design, devtools
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.