clean-code-dotnet VS zustand

More clean code concepts from this GitHub repo. Derived from Robert C. Martin's book Clean Code, adapted for .NET/.NET Core. There is also for JavaScript and PHP.

Clean code C sharp

I like the boilerplate that you can get on internet, GitHub has a lot of documentation, boilerplates and more the iOS , android app has an exploration repository where you can learn eg: https://github.com/thangchung/clean-code-dotnet

Maybe this repo can help too https://github.com/thangchung/clean-code-dotnet though I didn't check it personally.

For our case, points 1 and 2 can help us provide a better way of handling updates in our rapidly updating application. I have used zustand for the application.

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

Zustand

Link: https://zustand-demo.pmnd.rs/

For more code examples visit the documentation here

Have you ever wanted to learn state-management but it felt so overwhelming to get started with Redux? Or maybe you're already using Redux but don't want to take the burden anymore? If so, you might want to take a shot at Zustand! Its an amazing state management library that's easy to get started and maintain in a long run. In this post, we'll dive into creating & sharing stores with this tiny Redux alternative.

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

Zustand

I tried using skipHydration inside my zustand store based on their docs, then rehydrating it inside my modal. So far im getting the same errors. https://github.com/pmndrs/zustand/blob/main/docs/integrations/persisting-store-data.md