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
Hi! In some situations, to keep consistency, there is a need to use the same window namespace for custom solutions as we might use for assigning data via @javascript(). Current implementation of the module overrides data that have been declared before @javascript(). What do you think about appending data to the namespace if such already exists (and maybe even make it configurable?) instead of just clearing that?
The text was updated successfully, but these errors were encountered:
Hi! In some situations, to keep consistency, there is a need to use the same window namespace for custom solutions as we might use for assigning data via
@javascript()
. Current implementation of the module overrides data that have been declared before@javascript()
. What do you think about appending data to the namespace if such already exists (and maybe even make it configurable?) instead of just clearing that?The text was updated successfully, but these errors were encountered: