4 ms·
Heh, I made the same thing but with global endpoints and swappable drivers so that components can be shared and endpoints can be stubbed/mocked: https://gitHub.
by tonyhb 10y ago
Heh, I made the same thing but with global endpoints and swappable drivers so that components can be shared and endpoints can be stubbed/mocked: https://gitHub.com/tonyhb/tectonic https://gitHub.com/tonyhb/tectonic
Think that genraally we're learning that these things should be automated for us: loading data traditionally sucks. GraphQL is really where it's at!
edit: that mobile keyboard though...
- djmashko2 10y agoYeah, Apollo Client helps you do a lot of these kinds of things with GraphQL - deduplicating requests, keeping track of loading states, etc: dev.apollodata.com (disclaimer: I work on Apollo)
- ryanashcraft 10y agoAuthor here. I totally agree if you're starting a new project or have the bandwidth to migrate to GraphQL – definitely consider it! However, I still think we'll need solutions that work for apps that use non-GraphQL APIs.