data-client VS normalizr

Provides data fetching, but handles mutations better by using reactive paradigms.

You can still do SSR with normal client-side behavior if you use a React 18 SSR compatible library

https://resthooks.io/ is inspired by Backbone models

The control flow can be pretty straightforward once you have middleware integration; which you can see with async state management becoming as simple as a one-liner

You're probably better off using a tool that is built with code reuse in mind like https://resthooks.io

Probably the most important thing is to have a normalized data cache to save yourself tons of data-bug headaches. I use https://resthooks.io/ myself because it used inferred typing safety meaning I don't have to do any extra definitions or even use typescript and it will tell me what types I should expect. But you could also roll your own normalization using https://github.com/paularmstrong/normalizr with a state management tool like redux

If the data ever changes I prefer using Rest Hooks to ensure data integrity without having to manually write state updates for every usage

The advantage really comes when you using libraries like https://resthooks.io/ that enforce and infer strong types without effort from you. Then all you're doing is writing the types. Even cases like typos get removed due to typeahead helping you out. This is especially helpful in large projects with many developers as you'll likely be frequently working with types someone else defined and you don't know their members off the top of your head.

rest-hooks - Delightful data fetching for React.

Probably the most important thing is to have a normalized data cache to save yourself tons of data-bug headaches. I use https://resthooks.io/ myself because it used inferred typing safety meaning I don't have to do any extra definitions or even use typescript and it will tell me what types I should expect. But you could also roll your own normalization using https://github.com/paularmstrong/normalizr with a state management tool like redux

I’ve used this library to convert nested arrays fetched from an API into objects keyed by ID https://github.com/paularmstrong/normalizr

How can I assign id/slug related to the entity's parent using normalizr?

Having a bit of an issue trying to normalise a payload, that contains a nested schema of the same type as the parent using Normalizr

I'm going to go against the tide here and point out that GraphQL APIs aren't normalized, but GraphQL caching implementations end up normalizing GraphQL responses, so that's a large amount of prior-art that says "no." There are also tools like normalizr to make (de)normalization simple on the frontend.

This is already a thing a normalising library called Normalizr, usually normalising data into hash maps makes it really efficiently to work with it. It makes also working with state management a less tedious.

Redux Toolkit docs do have a page on Normalizing State Shape, and recommend the Normalizr library.

We've struggled with the navigation too. We rely on Interaction Manager and Pure component. We are trying to make sure no component should not render without a reason, we're still optimizing the app. I'd recommend this package called Why Did You Render. It helps us to find the culprit and mitigate it. And since our app is heavily relied upon Redux, we use normalizr for better optimization.

It's one of those things that makes your life a lot easier. Normalizr will help you with relationships.