-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Filter state properties like filtering components #401
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
Comments
I just have two sidenotes:
Have you actually applied the code outlined in vuex's docs for hot reloading? full page refreshs should not be necessary, usually. https://vuex.vuejs.org/en/hot-reload.html
This is generally not advised. State should be normalized if possible. I realize that this is not always possible and your situation might be one of those, but I thought to mention it. |
Nice, something I'll definitely try out.
Exactly. Imagine you have shop with a MongoDB database with redundancy and, like I do, one entity is mapped to one module. You may have something like this:
It would be nice to search for |
@yyx990803 this issue is not resolved. Or do you consider it implicitly resolved through #418? The behavior I would expect would the same as filtering components: The match jumps to the deepest possible child node. Like:
Becomes when searching for
|
Except it doesn't work like that. 😛
|
Problem: I have a complex and deep nested Vuex store. I often track those nested properties. The problem is now, every edit to the store requires a full page reload and the opened Vuex state is gone.
Feature request: It would be cool to search the store for properties like you can search components to quickly watch the desired nested property.
Might be a duplicate of #259, but the referenced issue with the referenced merge request didn't fulfill the feature request.
The text was updated successfully, but these errors were encountered: