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

fix: improve components removing behavior #31

Open
Gugustinette opened this issue Oct 30, 2024 · 0 comments
Open

fix: improve components removing behavior #31

Gugustinette opened this issue Oct 30, 2024 · 0 comments

Comments

@Gugustinette
Copy link
Contributor

When a component is removed :

  • Make sure callbacks are deleted and won't be called
  • Free objects in memory ?
  • Also add a destroy() method on components for convenience ?
@Gugustinette Gugustinette converted this from a draft issue Oct 30, 2024
@Gugustinette Gugustinette changed the title fix: make sure to free components that are removed fix: improve components removing behavior Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant