
* initial restructuring * add weights for ordering * fix links * remove aliases, add script Co-authored-by: Jack Baldry <jack.baldry@grafana.com> Co-authored-by: David Harris <david.harris@grafana.com> * make pretty * use correct link for angular to react guide * refactor: move the migration guide to /Developers * Revert "refactor: move the migration guide to /Developers" This reverts commit 8f31af8dfde3399060e8023c635174eb1243ae72. * fix: only redirect if the URL-hash has a valid redirect * fix: use a rel-ref for the Angular-React migration guide link * fix: update the hash redirects --------- Co-authored-by: David Harris <david.harris@grafana.com> Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
3.5 KiB
description | keywords | title | menutitle | weight | |||||
---|---|---|---|---|---|---|---|---|---|
Guide for migrating plugins from Grafana v8.x to v9.x |
|
Migrating plugins from Grafana version 8.x to 9.x | v8.x to v9.x | 2300 |
Migrating plugins from Grafana version 8.x to 9.x
9.0 breaking changes
theme.visualization.getColorByName replaces getColorForTheme
getColorForTheme
was removed, use theme.visualization.getColorByName
instead
Example:
// before
fillColor: getColorForTheme(panel.sparkline.fillColor, config.theme)
// after
fillColor: config.theme.visualization.getColorByName(panel.sparkline.fillColor),
VizTextDisplayOptions replaces TextDisplayOptions
TextDisplayOptions
was removed, use VizTextDisplayOptions
instead
Example:
// before
interface Options {
...
text?: TextDisplayOptions;
...
}
// after
interface Options {
...
text?: VizTextDisplayOptions;
...
}
Changes in the internal of backendSrv.fetch()
We have changed the internals of backendSrv.fetch()
to throw an error when the response is an incorrect JSON. Make sure to handle possible errors on the callsite where using backendSrv.fetch()
(or any other backendSrv
methods)
// PREVIOUSLY: this was returning with an empty object {} - in case the response is an invalid JSON
return await getBackendSrv().post(`${API_ROOT}/${id}/install`);
// AFTER THIS CHANGE: the following will throw an error - in case the response is an invalid JSON
return await getBackendSrv().post(`${API_ROOT}/${id}/install`);
GrafanaTheme2 and useStyles2 replaces getFormStyles
We have removed the deprecated getFormStyles
function from grafana-ui. Use GrafanaTheme2
and the useStyles2
hook instead
/api/ds/query replaces /api/tsdb/query
We have removed the deprecated /api/tsdb/query
metrics endpoint. Use [/api/ds/query]({{< relref "../../../http_api/data_source/#query-a-data-source" >}}) instead
selectOptionInTest has been removed
The @grafana/ui
package helper function selectOptionInTest
used in frontend tests has been removed as it caused testing libraries to be bundled in the production code of Grafana. If you were using this helper function in your tests please update your code accordingly:
// before
import { selectOptionInTest } from '@grafana/ui';
// ...test usage
await selectOptionInTest(selectEl, 'Option 2');
// after
import { select } from 'react-select-event';
// ...test usage
await select(selectEl, 'Option 2', { container: document.body });
Toolkit 9 and webpack
Plugins using custom Webpack configs could potentially break due to the changes between webpack@4 and webpack@5. Please refer to the official migration guide for assistance.
Webpack 5 does not include polyfills for node.js core modules by default (e.g. buffer
, stream
, os
). This can result in failed builds for plugins. If polyfills are required it is recommended to create a custom webpack config in the root of the plugin repo and add the required fallbacks:
// webpack.config.js
module.exports.getWebpackConfig = (config, options) => ({
...config,
resolve: {
...config.resolve,
fallback: {
os: require.resolve('os-browserify/browser'),
stream: require.resolve('stream-browserify'),
timers: require.resolve('timers-browserify'),
},
},
});
Please refer to the webpack build error messages or the official migration guide for assistance with fallbacks.