Kinto/kinto

Investigate how GraphQL could look like

Open

#810 建立於 2016年9月9日

在 GitHub 查看
 (2 留言) (8 反應) (0 負責人)Python (4,291 star) (425 fork)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!

貢獻者指南

技術棧
pythongraphql
領域
apibackend
議題類型
research
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
PythonGraphQL basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
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.