VizPanel: Fixes issue updating instanceState #702
Merged
Conversation
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
torkelo
added
release
|
🚀 PR was released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Trying to fix grafana/grafana#86554
Also changing / skipping using instanceState for legacyPanelId as this is a bit problematic as this state is really reserved to only be used by the panel plugin so for Grafana to use it causes issues (we have to make sure we preserve legacyPanelId when we handle onInstanceStateChange.
I am tempted to just add legacyPanelId to VizPanel state (instead of parsing it from key) but not sure.
📦 Published PR as canary version:
4.12.0--canary.702.8784713837.0✨ Test out this PR locally via:
npm install @grafana/scenes@4.12.0--canary.702.8784713837.0 # or yarn add @grafana/scenes@4.12.0--canary.702.8784713837.0