Conversation
Without keys, Vue reuses row component instances by index: disabling site A under 'Show enabled only' removes its row, and site B inherits A's switch instance still showing off - while the data (and backend) correctly have B enabled. Enabling the phantom-disabled B then really disables it. Tying each switch to its site id forces a fresh instance per row so the rendered state always follows the data. Assisted-By: muse-spark-1.3 Coauthored-By: XbvrDFAgent
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2286. Single-file, four-attribute change — nothing else piggybacked.
Verified by click-through on a fork build: disabling a site under 'Show enabled only' no longer leaves the next site rendering as disabled.