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.

Sign up for GitHub

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

Jump to bottom

Reatom migration #42

Open
Bricks666 opened this issue Jun 12, 2024 · 0 comments
Open

Reatom migration #42

Bricks666 opened this issue Jun 12, 2024 · 0 comments
Assignees
@Bricks666
Labels
migration Something about tools and libs changing

Comments

@Bricks666
Copy link
Owner

Think about migration from @effector to @reatom. Reatom looks more powerful and flexible for the app. There have already been problems with data and logic in reason of way effector works
@Bricks666 Bricks666 added the migration Something about tools and libs changing label Jun 12, 2024
@Bricks666 Bricks666 self-assigned this Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Bricks666 Bricks666

Labels
migration Something about tools and libs changing
Projects
ABCTasks
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Bricks666