Example: Add frontend migration example #335
Draft
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
andresmgot
changed the title
3 tasks
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.
Example of how a change in the API + migration code may look in a plugin.
Note that this assumes that the plugin uses a schema and a API version. See this base PR.
In this case, I am deprecating the field
multiplierof the QueryData and renamed itmultiply. Now both properties are optional, to avoid breaking changes in theapiVersion.Note that the query is automatically migrated when running a query but it's necessary for the plugin to manually call
migrateQueryin theQueryEditorto ensure that it's using the latest version of the Query schema.This is a demonstration for grafana/grafana#90231