At this point you probably understand the benefits of using immutable data structures. However, you might not understand the tradeoffs between different immutable libraries. Well, look no further. Here's a trade-off comparison of Immutable.js, Seamless-immutable and Timm
If you're building a component and using any in-line styles and you're not careful you can lock the consumer of you're component out of potential customizations they may require for their specific use-case (that you can't think of or foresee). Trying to build components to be reusable and a little more OCP can be challenging especially with how difficult it can be to get css layouts the way you (or the consumer of you're component) may want...
When attempting to use React, it's not always obvious to know how to interact with different types of backends. This article takes us through working with ASP.NET and React.
This article is about the benefits of using the Redux library in your React application, followed by a detailed description on how to use Redux. These descriptions use code snippets from a open-source sample application which contains a React application called Kanban inside a ASP.NET Core web application.
"State management is hard. And a lot of very smart and very vocal people each have their own opinion on the best way it should be done. Unfortunately, people gravitate towards loud voices and shiny things, even when the blunt hammer drives the straightest nail."
In React, you're left to your own devices in a lot of ways, sometimes it's great, but sometimes it sucks. Writing forms seems to be one of those sucky things to do in React. Do you use defaultValue? Mirror your form value with your state? Use a <form> ref?
Mobx is a really simple api for managing application state, similar to redux, and it can help you better manage your forms.