Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Refactor State Management: Migrate from Context API to Zustand #243

Open
1 task done
Prathamm-sahu opened this issue Feb 25, 2025 · 0 comments · May be fixed by #248
Open
1 task done

[FEATURE] Refactor State Management: Migrate from Context API to Zustand #243

Prathamm-sahu opened this issue Feb 25, 2025 · 0 comments · May be fixed by #248
Labels
enhancement New feature or request

Comments

@Prathamm-sahu
Copy link
Contributor

Problem or Use Case

Currently, the application uses Context API for state management, which leads to unnecessary re-renders and performance bottlenecks as the app scales. Since React re-renders the entire subtree when the context updates, it can cause performance degradation. This issue proposes migrating to Zustand, a lightweight and more efficient state management library that avoids these drawbacks.

Proposed Solution

  • To overcome these problems we should add Zustand a lightweight and more efficient state management library.
  • Zustand only updates components that are consuming the changed state, avoiding unnecessary re-renders.
  • It is more simpler and easier to use with better developer experience, reduced complexity and improved maintainability.

Are you willing to contribute?

  • Yes, I'd like to help implement this feature.

Additional Context

No response

@Prathamm-sahu Prathamm-sahu added the enhancement New feature or request label Feb 25, 2025
@Prathamm-sahu Prathamm-sahu linked a pull request Feb 26, 2025 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

1 participant