-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
"stores" tab #176
Comments
Update: stores are a v3 concept I'm not 100% sure how we can detect/list them if someone else has any ideas feel free to comment. |
There is a private |
This is my bad solution: First the extension adds a hidden Alpine initialized field in the body. <input
type="hidden"
x-title="_devtools_stores"
x-effect="new_store = { ...$store }; delete new_store._devtools_stores; $store._devtools_stores = new_store"
x-data="{new_store: null}"
/> The extension can then show all the stores data from From devtools Components page, element with name of Alpine.js should not start recursively looking for changes in |
@Niush Just tried that, doesn't seem to be working with devtools. EDIT: <input
type="hidden"
x-title="_devtools_stores"
x-effect="new_store = { ...$store }; delete new_store._devtools_stores; $store._devtools_stores = new_store"
x-data="{new_store: null}"
/> |
yeah! a $store Tab will be awesome! |
Devtools can have a "stores" tab
Spruce has a methods (outside of Alpine) for:
Object.keys(Spruce.stores)
("stores" > "spruce" so that we're forward compatible if stores make it into v3)
Originally posted by @HugoDF in #175
The text was updated successfully, but these errors were encountered: