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
Currently I have a top layer component called <CascadingState> where I provide for common state for every part of the webapp, and there do reside all the <Meta> tags(so I don't need to repeat them for each page) that seem to work fine when a page is loaded with forceReload or it's customized within that same page, updating those tags values in real time.
But the common navigation seem to reset the state of <Meta> tags to the default values(of the original index.html).
Then obviously each page has <Title> that setups the state of the title alone.
So my final guess is that you can't really separate the states in the way that I did, and the latest activated component does override everything, so I guess I'm gonna write a component to manage in a tight ways such repetitive state and let you all know.
The text was updated successfully, but these errors were encountered:
Honestly, I'd never considered this scenario that you said.
But anyway, I've been started to be interested in supporting this scenario and resolving this issue.
By the way, I can not work on this issue right now, unfortunately.
Because I already have some unresolved feedbacks in my repositories even though now is the Christmas holiday season!
So I would appreciate it if you waited for my work to be finished.
Currently I have a top layer component called
<CascadingState>
where I provide for common state for every part of the webapp, and there do reside all the<Meta>
tags(so I don't need to repeat them for each page) that seem to work fine when a page is loaded with forceReload or it's customized within that same page, updating those tags values in real time.But the common navigation seem to reset the state of
<Meta>
tags to the default values(of the originalindex.html
).Then obviously each page has
<Title>
that setups the state of the title alone.So my final guess is that you can't really separate the states in the way that I did, and the latest activated component does override everything, so I guess I'm gonna write a component to manage in a tight ways such repetitive state and let you all know.
The text was updated successfully, but these errors were encountered: