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
Actually, Nalu will always update the DOM, even if the element, that will be display for the next route is the same one, that will be attached for the new route. Even, if the caching feature is used, a detach and attach will be done.
To tell Nalu, to reuse an existing component (which is already attached to the DOM), a new attribute is used: creationMode.
The creationMode has two possible values:
CREATE: Nalu will always attach and detach the component. With this value, Nalu behave in the same way as it does today.
REUSE: Choosing this value, Nalu will reuse element in case it is already attach to the DOM. In this case, Nalu will not do a detach/attach for the component of the new route if it is already attached.
The text was updated successfully, but these errors were encountered:
commit 57b18aa
Author: FrankHossfeld <[email protected]>
Date: Wed Apr 15 08:04:52 2020 +0200
# 127 - Reuse elements in case route does not change
commit 33038ff
Author: FrankHossfeld <[email protected]>
Date: Wed Apr 15 08:02:31 2020 +0200
# 127 - Reuse elements in case route does not change
Actually, Nalu will always update the DOM, even if the element, that will be display for the next route is the same one, that will be attached for the new route. Even, if the caching feature is used, a detach and attach will be done.
To tell Nalu, to reuse an existing component (which is already attached to the DOM), a new attribute is used:
creationMode
.The
creationMode
has two possible values:CREATE
: Nalu will always attach and detach the component. With this value, Nalu behave in the same way as it does today.REUSE
: Choosing this value, Nalu will reuse element in case it is already attach to the DOM. In this case, Nalu will not do a detach/attach for the component of the new route if it is already attached.The text was updated successfully, but these errors were encountered: