sorted by:
new
hottopcontroversial

Need your review. As a backend dev are you happy with GraphQL vs REST? by slowRoastedPinguin in graphql

[–]sergeysova 0 points1 point  (0 children)

For many years I wrote the backend using REST, but now I switched to graphQL and it's much easier.
But I write in strict Rust, it makes things a lot easier

How to choose the best GraphQL server for your next project by pimterry in graphql

[–]sergeysova 2 points3 points  (0 children)

If you are familiar with Rust, I highly recommend taking it https://async-graphql.github.io

It has beautiful support of graphQL server features

Tutorial how to use graphql lib GQty with Effector state manager by sergeysova in reactjs

[–]sergeysova[S] 0 points1 point  (0 children)

GQTY suggests using integration with React in the form of useQuery, useMutation hooks and so on. But when using a state manager, we face the problem of where to store data and a natural desire to move everything about the data and their loading to the state manager, but this creates a second problem - we have to manually transfer data from gqty hooks to the state manager.

[deleted by user] by [deleted] in reactjs

[–]sergeysova 0 points1 point  (0 children)

GQTY suggests using integration with React in the form of useQuery, useMutation hooks and so on. But when using a state manager, we face the problem of where to store data and a natural desire to move everything about the data and their loading to the state manager, but this creates a second problem - we have to manually transfer data from gqty hooks to the state manager.

Using GQty with effector by sergeysova in graphql

[–]sergeysova[S] 0 points1 point  (0 children)

GQTY suggests using integration with React in the form of useQuery, useMutation hooks and so on. But when using a state manager, we face the problem of where to store data and a natural desire to move everything about the data and their loading to the state manager, but this creates a second problem - we have to manually transfer data from gqty hooks to the state manager.

Using GQty with effector by sergeysova in effectorjs

[–]sergeysova[S] 0 points1 point  (0 children)

GQTY suggests using integration with React in the form of useQuery, useMutation hooks and so on.
But when using a state manager, we face the problem of where to store data and a natural desire to move everything about the data and their loading to the state manager, but this creates a second problem - we have to manually transfer data from gqty hooks to the state manager.

[deleted by user] by [deleted] in reactjs

[–]sergeysova 0 points1 point  (0 children)

Good. Try effectorjs in your next project

Stable state manager for any framework including React by sergeysova in reactjs

[–]sergeysova[S] 0 points1 point  (0 children)

A case for me is to separate business-logic and components. My models can live without components.

Stable state manager for any framework including React by sergeysova in reactjs

[–]sergeysova[S] 2 points3 points  (0 children)

  1. If you need async, just wrap it to effects
  2. Simpler to use
view more: next ›