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

Mutating an atom after the app is created but before mounting breaks reactivity #862

Open
kasperskei opened this issue Jun 7, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@kasperskei
Copy link
Contributor

What happened?

Example

Part

Package @reatom/jsx

Version

3.10.0

What browsers are you seeing the problem on?

No response

Relevant log output

No response

@kasperskei kasperskei added the bug Something isn't working label Jun 7, 2024
Copy link

stackblitz bot commented Jun 7, 2024

Fix this issue in StackBlitz Codeflow Start a new pull request in StackBlitz Codeflow.

@artalar
Copy link
Owner

artalar commented Jun 11, 2024

The are a problem. We can't subscribe to not mounted elements to prevent memory leaks, but if we will parse all subtree on each mount / conditionally added element - it will take a lot of extra costs. I will think about it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants