apollo-client-devtools VS starter

This call creates canonical field allTodos on the root Query type. We can confirm this by opening apollo devtools and viewing the 'cache' tab.

People don't understand how their code can mess up others in unexpected ways. A few weeks ago my youtube just stopped working. Turns out, a change made to the apollo-graphql extension caused window.process to be readonly and youtube's code was not expecting that: https://github.com/apollographql/apollo-client-devtools/issu...

I know this isn't a dependency issue, but it's a great example of why things like semver don't work perfectly in practice. It's hard to figure out what the effects of your code really are in the end. You might assume a change is minor when it really is major. I wish programming languages could figure out what the version change should be for a given code change.

Do you perhaps use chrome and have apollo client dev tools installed? They break import maps, which breaks the site, see here: https://github.com/apollographql/apollo-client-devtools/issues/464

It's so weird that this seems like a common use case but across the 3 channels I've asked (also asked on the official Apollo Spectrum chat & SO) it's radio silence beyond your reply! To add insult to injury, Apollo devtools was updated over the weekend and broke for v2 clients! Argh!!

I've been enjoying developing on top of PostGraphile. https://www.graphile.org/

Good starter: https://github.com/graphile/starter

I can add a column the the db, and my frontend gets that autimagically (in dev mode, it generates a graphql schema out of the db, and from that it creates composables for my frontend wiht graphql-codegen). On the frontend I use Vue 3, the starter is build with nextjs/react.

I learned so much about postgresql and RLS from postgraphile starter project: https://github.com/graphile/starter/blob/main/%40app/db/migr...

also the project is worth checking out ;)

I'm a fairly seasoned developer, but I've started contributing to a project (graphile-starter) where the core business logic is defined in PL/pgSQL functions and realized I have a lot to learn.

Someone called it: "hasura for adults”

It's highly customisable, works directly with postgresql row levels security and the performance is quite good. It has a custom GraphiQL gui to work on queries/mutations.

To really see how it all works together checkout the starter project: https://github.com/graphile/starter it has migrations, job queue, graphql-codegen etc.

Benjie (https://github.com/benjie) is one of the greatest maintainers I've ever seen!

Here’s a full stack, batteries included example: https://github.com/graphile/starter it doesn’t have mobile app yet but could be added relatively easily.

Postgraphile starter uses most of the same tech and has all the same functionality as far as I can tell, with the additional benefit of Postgraphile generating your GraphQL schema and resolvers instead of worrying them manually.

Check out the Postgraphile Starter and how it handles auth and sessions in a graphql api