Open oohwooh opened 1 year ago
instead of react-query, moving topo to use apollo client would also be an option, not sure what the performance different is. https://www.apollographql.com/docs/react/data/queries/
okay nvm actually, nextjs app directory looks like the right answer to this. it would allow for almost the same as react-query but probably more efficient
At some point, I want to port clear to Typescript, using graphql-codegen and react-query
Additionally, I am also working on a more advanced system for CRUD forms using gql-codegen and RJSF for a separate project. This should be relatively easily portable to clear, and will provide a lot of improvements to the developer and user experience when it comes to CRUD forms.
react-query will allow us to move away from server side rendering + data fetching, which should improve the perceived speed of the site significantly, and reduce our fly bill.
Another huge benefit of react-query is it allows us to mock data, drastically lowering the barrier of entry to potential contributors. (Right now we either need to give them private keys + admin token, or for them to run
gql-server
and all other microservices locally)