You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is reported that there is a possibility to use graphcool serverless back-end with Gatsby via gatsby-source-graphcms plugin. gatsbyjs/gatsby#1127 (comment)
I'd like to explore this possibility in depth.
If it works, we can avoid hacking Gatsby in order to connect with Apollo(There is no nice and official way to connect Apollo with Gatsby ).
We will not need Apollo longer and the state will go to Redux. 👏
The text was updated successfully, but these errors were encountered:
This seems to be a long-running issue, is this for storing content? Or for querying data? Either way there's always GraphCMS have either of you (@mar-bi , @miljan-fsd ) used it?
We considered graphcool backend for CRUD operation. Maybe without D. 😄
I had a first look at the suggested GraphCMS headless back-end and found it promising.
We may use it instead of Contentful and graphcool. 🤔
We need to explore it in details. 🔎
It is reported that there is a possibility to use
graphcool
serverless back-end withGatsby
viagatsby-source-graphcms
plugin.gatsbyjs/gatsby#1127 (comment)
I'd like to explore this possibility in depth.
If it works, we can avoid hacking
Gatsby
in order to connect withApollo
(There is no nice and official way to connectApollo
withGatsby
).We will not need
Apollo
longer and the state will go toRedux
. 👏The text was updated successfully, but these errors were encountered: