-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
25 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a4eec41
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello again!
Since the advent of vuex-next, I began to rewrite (rather large) my application on vue 3 and at the moment I have already implemented the basis of the application and it can already be used.
I started switching to vue 3 too early, because for some very important features I needed Fragment support (some of which I already implemented).
However, I have one (and only) vue issue - there is no KeepAlive support for RouterView. Complex problems arise from this:
In all the rest, by the way, there really are no problems and everything works quickly and cool :)
I ask you to start implementing KeepAlive support as early as possible, because it greatly affects my project.