make pretty

2023-04-11 13:26:16 +02:00
parent 8964812375
commit 04c30aa19b
7 changed files with 7 additions and 6 deletions
@@ -36,4 +36,4 @@ title: Migration guides

 The following guides help you identify the steps required to update a plugin following changes between versions of Grafana.

-{{< section menuTitle="true">}}
+{{< section menuTitle="true">}}
@@ -70,4 +70,4 @@ While all plugins are different, we'd like to share a migration process that has

 By now, you should be able to release your new version.

-To fully migrate to the new plugin platform, convert the time series response to a data frame response.
+To fully migrate to the new plugin platform, convert the time series response to a data frame response.
@@ -117,4 +117,4 @@ import { VizLegendItem, VizLegendOptions, VizLegend } from '@grafana/ui';
 ```

 - `LegendPlacement` has been updated from `'under' | 'right' | 'over'` to `'bottom' | 'right'` so you can not place the legend above the visualization anymore.
- The `isVisible` in the `LegendItem` has been renamed to `disabled` in `VizLegendItem`.
+- The `isVisible` in the `LegendItem` has been renamed to `disabled` in `VizLegendItem`.
@@ -346,3 +346,4 @@ function Component(): ReactElement | null {
    </NonMigrate>
  );
 };
+```
@@ -96,4 +96,4 @@ getLocationSrv.update({

 // after
 locationService.partial({ 'var-variable': 1 }, true);
-```
+```
@@ -109,4 +109,4 @@ module.exports.getWebpackConfig = (config, options) => ({
 });
 ```

-Please refer to the webpack build error messages or the [official migration guide](https://webpack.js.org/migrate/5/) for assistance with fallbacks.
+Please refer to the webpack build error messages or the [official migration guide](https://webpack.js.org/migrate/5/) for assistance with fallbacks.
@@ -145,4 +145,4 @@ It's recommended to use the `<request>.GetHTTPHeader` or `<request>.GetHTTPHeade

 The grafana-plugin-sdk-go [v0.147.0](https://github.com/grafana/grafana-plugin-sdk-go/releases/tag/v0.147.0) introduces a new interface [ForwardHTTPHeaders](https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go@v0.147.0/backend#ForwardHTTPHeaders) that `QueryDataRequest`, `CheckHealthRequest` and `CallResourceRequest` implements.

-Newly introduced forwarded HTTP headers in Grafana v9.4.0 are `X-Grafana-User`, `X-Panel-Id`, `X-Dashboard-Uid`, `X-Datasource-Uid` and `X-Grafana-Org-Id`. Internally these are prefixed with `http_` and sent as `http_<HTTP header name>` in [CheckHealthRequest.Headers](https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go@v0.147.0/backend#CheckHealthRequest) and [QueryDataRequest.Headers](https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go@v0.147.0/backend#QueryDataRequest). By using the [ForwardHTTPHeaders](https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go@v0.147.0/backend#ForwardHTTPHeaders) methods you're guaranteed to be able to operate on HTTP headers without using the prefix, i.e. `X-Grafana-User`, `X-Panel-Id`, `X-Dashboard-Uid`, `X-Datasource-Uid` and `X-Grafana-Org-Id`.
+Newly introduced forwarded HTTP headers in Grafana v9.4.0 are `X-Grafana-User`, `X-Panel-Id`, `X-Dashboard-Uid`, `X-Datasource-Uid` and `X-Grafana-Org-Id`. Internally these are prefixed with `http_` and sent as `http_<HTTP header name>` in [CheckHealthRequest.Headers](https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go@v0.147.0/backend#CheckHealthRequest) and [QueryDataRequest.Headers](https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go@v0.147.0/backend#QueryDataRequest). By using the [ForwardHTTPHeaders](https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go@v0.147.0/backend#ForwardHTTPHeaders) methods you're guaranteed to be able to operate on HTTP headers without using the prefix, i.e. `X-Grafana-User`, `X-Panel-Id`, `X-Dashboard-Uid`, `X-Datasource-Uid` and `X-Grafana-Org-Id`.