Investigate how GraphQL could look like · Kinto/kinto#810

2016-09-09T13:02:03.000Z

- 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! - See http://graphene-python.org

(2 comments) (8 reactions) (0 assignees)Python (4,291 stars) (425 forks)batch import

help wantedplugin-ideastale

説明

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!

See http://graphene-python.org

コントリビューターガイド

技術スタック: pythongraphql
領域: apibackend
Issue 種別: research
難度: 3
推定時間: 1-2 days
活動状況: stale
明確さ: needs investigation
前提条件: PythonGraphQL basics
初心者向け度: 30
調査方針: 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.