normalizr VS Immer

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.

Immer is a lightweight package that simplifies working with immutable states. Immutable data structures ensure efficient data change detection, making it easier to track modifications. Additionally, they enable cost-effective cloning by sharing unchanged parts of a data tree in memory.

```

It looks like it’s mutating, but both the reducers and update() uses immer* under the hood, so we still respect immutability under the hood.

Cami supports redux devtools so you can use that for time-travel debugging too!

—-

* https://github.com/immerjs/immer

I heard that immutability libraries like immer.js [0] help with this. Anyone go this way and had good success? Is this 'the way'?

[0]: https://immerjs.github.io/immer/

So, that's what we built, and we built it in the most obvious way — using JavaScript Proxy objects to track mutations and reflect those changes across Appsmith’s framework. Initially things looked good — it worked, aside from a few hacks to make some data types work with map and set, and we were following the example of other projects that had similar requirements. If it was good enough for them, it should be good enough for us, right?

But is immer really the ultimate answer? The performance problem of immer is more prominent in large arrays and deep-level object scenarios. See this issue description, many authors in the community began to try to make breakthroughs, and noticed that structura and mutative, I found that it is indeed many times faster than immer as they said, but it still fails to solve the problem of both fast speed and good development experience. I will analyze the two issues in detail below.

I like immer for this kind of thing: https://github.com/immerjs/immer

It gives you immutable updates without getting bogged down in FP abstractions.

I've always been a huge fan of immer for these case. For your code, it would simply turn into setGridData((prev) => produce(prev, draft => applyChanges(changes, draft)) but I recommend you go over their documentation to fully understand how it works

If you're trying to make things actually immutable, Object.freeze and deep copies can clutter things up pretty good, have you considered using something like immer? (https://immerjs.github.io/immer/)