Kinto/kinto

Investigate how GraphQL could look like

Open

#810 opened on Sep 9, 2016

View on GitHub
 (2 comments) (8 reactions) (0 assignees)Python (4,291 stars) (425 forks)batch import
help wantedplugin-ideastale

Description

  • We have flat collections of records
  • We have JSON schemas
  • It seems very reasonnable to think that resolving a GraphQL query using our data model is feasible
  • Queryable APIs are really becoming a thing, and it would make sense for a «reusable storage backend» to offer that
  • Clients like Relay can do very powerful stuff for caching locally and syncing trees of data

Let's discuss and POC something!

Contributor guide

Tech stack
pythongraphql
Domain
apibackend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
PythonGraphQL basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Start by reviewing Kinto's data model (flat collections of records with JSON schemas) and the graphene python library. Prototype a simple GraphQL endpoint that resolves queries from Kinto's storage. The issue's discussion and linked resources (e.g., graphene python.org) provide initial direction. Focus on mapping existing REST endpoints to GraphQL types and resolvers.