-
Notifications
You must be signed in to change notification settings - Fork 41
GraphQL API server RFC #22
base: master
Are you sure you want to change the base?
Conversation
Great stuff! While Gatsby can be used for the web, it currently doesn’t offer a solution for native apps AFAIK (or does it?). If Gatsby’s data layer could be run as a backend it could help a lot. Not quite clear how authentication would be handled though. Our app is available through web, iOS and Android so I’d be really excited to see this happening. We have a PostgreSQL database, so Gatsby could sit in front of it with gatsby-source-pg (or using Prisma, Hasura etc), alongside other sources stitched together by Gatsby, and the whole thing would be available to web, iOS and Android clients. |
Interesting, I haven't considered that use case yet, but it's certainly a huge one. I mainly focused on using the data in projects that are already static Gatsby apps. I also haven't thought much about authentication yet, IMHO we should not implement any auth in the core |
309f6f9
to
9c7253d
Compare
Added new drawback:
|
@jgierer12 That seems solvable — if we see the query being used elsewhere, we could preserve it instead of removing it during the build. There might be some restrictions I'm not aware of, but I think we could definitely fix this without requiring duplicated queries. |
RFC for gatsbyjs/gatsby#10230.
View text