You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
What were the main benefits driving this architectural change?
What were the key considerations in choosing this implementation?
Are there any performance implications to consider?
This would be valuable documentation for other developers who might have similar questions about this design decision.
The text was updated successfully, but these errors were encountered:
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:
This would be valuable documentation for other developers who might have similar questions about this design decision.
The text was updated successfully, but these errors were encountered: