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

Recoil Package Migration #3457

Open
6 tasks
mrCherry97 opened this issue Nov 7, 2024 · 0 comments
Open
6 tasks

Recoil Package Migration #3457

mrCherry97 opened this issue Nov 7, 2024 · 0 comments

Comments

@mrCherry97
Copy link
Contributor

mrCherry97 commented Nov 7, 2024

Description
The current global state management in our React application is handled by the Recoil package. However, there have been reports of memory leaks associated with Recoil, leading to potential performance and stability issues. In order to address this concern, a validation of the migration from Recoil to an alternative global state management solution is necessary.

The validation process will involve ensuring that the migration is successful without any loss of functionality or data. The new global state management solution should provide equivalent or improved performance compared to Recoil and should effectively eliminate any memory leaks that were previously experienced.

The validation process is crucial to ensure that the proposed migration will address the existing issues and improve the overall performance and stability of the application. Upon successful validation, the migration to the alternative global state management solution can be implemented to enhance the reliability and efficiency of our application.

Acceptance Criteria

  • Successful migration from Recoil package to an alternative global state management solution.
  • All existing functionality and data must remain intact post-migration.
  • Performance of the alternative solution should be equal to or better than Recoil.
  • Ensure that memory leaks previously experienced with Recoil are no longer present with the new solution.
  • Compare the capabilities and features of the alternative solution with Recoil, outlining the advantages and disadvantages of each in terms of scalability and maintainability.
  • Evaluate the developer experience and ease of use for the alternative solution compared to Recoil, highlighting the advantages and disadvantages of each in terms of development workflow and tooling support.

Reasons

  1. Recoil package has been known to cause memory leaks which can adversely impact application performance and stability.
  2. Exploring an alternative global state management solution can help address the memory leak issue and provide a more reliable and efficient solution for the application.
  3. Validation of the migration is necessary before implementing the change to ensure a seamless transition with minimal disruptions to the application.
  4. The recoil package is no longer maintained.

Attachments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant