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

Explain benefits of representing fragment as custom element #207

Open
Guria opened this issue Nov 3, 2024 · 0 comments
Open

Explain benefits of representing fragment as custom element #207

Guria opened this issue Nov 3, 2024 · 0 comments

Comments

@Guria
Copy link
Contributor

Guria commented Nov 3, 2024

In v4.6.0, Fragments are now implemented using a custom HTML element (<lustre-fragment>) instead of the previous virtual DOM abstraction that didn't introduce wrapper elements.

Given that a key purpose of Fragments is typically to avoid introducing wrapper elements in the DOM tree, I'd like to understand:

  1. What were the main benefits driving this architectural change?
  2. What were the key considerations in choosing this implementation?
  3. Are there any performance implications to consider?

This would be valuable documentation for other developers who might have similar questions about this design decision.

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

No branches or pull requests

1 participant