Unless it's angular

@@user-ez6xb3rf3p AnGuLaR IsN'T A LiBrArY, iT'S A FrAmEwOrK

@@user-ez6xb3rf3p bruhh. He is just saying his opinion and its more like a joke at this point

don't forget to follow me on twitter too ;) twitter.com/benawad/status/1185771363388346369

👍

lmao

Thank you 🙂

thanks

guyman8282 I like that stack a lot but I’m wondering how you handle offline and sync merge conflicts without using appsync

Thanks!

I'm using it and albeit I'm finding some bumps along the way, all of them so far were related to the learning curve :) It's actually quite awesome.

this is where graphql-playground comes in handy to see the entire schema I actually like code-first better for large projects because the typedefs and resolvers are together

You can pick which fields you expose from the database and still share models

@@bawad That is true for TypeORM in this case, but my point was more that you could use GraphQL to define the data that your UI needs, rather than defining the schema 1:1 with the database. Coupling GraphQL to your database has its drawbacks. First, you leak information about _how_ your data is stored, rather than _what_. This can make it difficult to keep a consistent schema across services and databases. It also makes scaling very hard when using different data sources. You'll need to define a source of truth for what data is available. I say this from my experience working with GraphQL and a variety services with different databases and endpoints. We ended up with a single GraphQL schema that defined the data that should be available in the UI. Types can be based on the data that different services provided, and the resolvers would take care of fetching and prepare the data when being queried. This also tied perfectly in with caching as we can use the schema to verify the schema of data in cache (using in-house tools) and deprecate anything with GraphQL if needed.

yeah that's a good point, there are times where the data needs for the UI are totally different from the database

when I learn serverless, sure

There many useful hidden features. For example, whenever you update PostgreSQL schema (migration), it automatically updates all the TypeScript definitions for db tables and enums (see yarn db:reset).

1. I like to use middleware for this 2. for local state I use useState/useReducer

@@bawad Could you elaborate on how you use `useState`/`useReducer` together with your choice of graphql client/server libs?

I don't mix them. If I need data from the api I use apollo if I need local state I do useState/useReducer

Niwat A he already did a video a month ago about jwt, graphql and react.

It is sometimes Gatsby is a good choice

sorry, don't have any experience with offline syncing

I don't know of any benchmarks either but graphql is slower . For most applications it should negligible

I liked it for REST, but didn't find it useful for graphql

I haven't, I usually use useState/useReducer for local state with graphql

@@bawad okay great, i was looking into it.thanks

i think you can use the zustand

1. I don't 2. yes

Yeah it was unmaintained for a while, but I think it's getting some attention now. But yeah that part of it is unfortunate. If you could mix GraphQL with the Objection/Knex models I would recommend them, but right now only typeorm can do that

you can use any db with graphql including mysql

@@bawad Oh, thanks

Haven't done any videos specifically with join-monster/dataloader and typegraphql, but it should be the same kzfaq.info?search_query=benawad+dataloader

iso formatted string

I'm working on www.mysaffronapp.com/ fulltime and youtube part time. I have money saved up from consulting + some comes from youtube ads / patreon

Idk I've never tried firebase

Found an article that might help: codeburst.io/using-dataloader-with-graphql-a-concrete-example-9b21352f1676.

here's one example of how I do it: kzfaq.info/get/bejne/layBZL12vK_SYqc.html

I think realm is dead

1. didn't want to write postgres functions 2. didn't want to use serverless

I really love hasura, but the biggest problem is auth. Another problem is I don't wanna use many serverless functional, so I'm wondering if I should write native postgres functions in my datadata to achieve some business logic.