Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Ensure that a unique, serialized key is only created once per navigateTo #818

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

Conversation

tylerflint
Copy link

When using navigateTo, there are certain conditions which can force the render() function of the navEntryInstance to be called multiple times. The problem is that a key is generated during the render function, and the key generation function has a global incrementing counter. When this occurs, a new navEntryItem is created, which the frame seems to dump promptly, or Vue ignores.

To be honest I haven't delved deeply into the inner working of the frame, or really understood how the render function gets called multiple times. Regardless, it does and ensuring that a unique key is only generated once will keep Vue happy.

…eTo page, even when render is called multiple times
@rigor789
Copy link
Member

rigor789 commented Mar 9, 2021

Thanks - this is a nice find! I actually just merged a similar fix: #814 so I'll close this one.

@rigor789 rigor789 closed this Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants