-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Vuex: keep inspected mutation selected if there is a new mutation #925
Comments
IMHO Seems more like a bug than an enhancement, since viewing state is pretty much unusable, and it’s also a regression of behaviorfrom prior dev tools version. |
I have to agree with @jacobg |
@jacobg Git agrees with me that the inspected mutation was always reset to the last one when a mutation was received, even 2 years ago 😸️ |
@Akryum Thanks for resolving. I thought I remember in the old version I could look at state even when new mutations come in. Perhaps the state was getting updated with new mutations. The current version changes to Loading State spinner when new mutation comes in. |
@jacobg I think your are talking about something different, OP was about selecting a mutation other than the last one and keeping it selected when a new mutation is received. |
…ess it was the last one, closes vuejs#925
Version
5.0.3
Browser and OS info
Chrome / Windows 10
Steps to reproduce
setInterval
that updates the state via a mutation at a regular intervalWhat is expected?
If an entry in the vuex log is explicitly clicked on to be inspected, it shouldn't be changed due to a mutation.
What is actually happening?
When a mutation occurs the 'inspected' Vuex item is updated to the latest value
I added a screen capture of what is occurring here: https://imgur.com/a/QfKAI9N
The text was updated successfully, but these errors were encountered: