IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-02-25 18:55:37 -06:00
Code Issues Packages Projects Releases Wiki Activity

Scenes: Fix angular migrations that are using the targets property on the old panel model (#96626)

Browse Source 
Fix angular migrations using target
This commit is contained in:
Oscar Kilhed 2024-11-20 09:52:52 +01:00 committed by GitHub
parent be59a6113b
commit 5986b03a8f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
public/app/features/dashboard-scene/serialization/angularMigration.ts
View File

@ -1,4 +1,4 @@
import { defaults } from 'lodash';
import { defaults, cloneDeep } from 'lodash';
import { PanelModel as PanelModelFromData, PanelPlugin } from '@grafana/data';
import { autoMigrateAngular, PanelModel } from 'app/features/dashboard/state/PanelModel';
@ -12,6 +12,17 @@ export function getAngularPanelMigrationHandler(oldModel: PanelModel) {
if (!oldModel.options || Object.keys(oldModel.options).length === 0) {
defaults(panel, oldModel.getOptionsToRemember());
// Some plugins rely on being able to access targets to set up the fieldConfig when migrating from angular.
const targetClone = cloneDeep(oldModel.targets);
Object.defineProperty(panel, 'targets', {
get: function () {
console.warn(
'Accessing the targets property when migrating a panel plugin is deprecated. Changes to this property will be ignored.'
);
return targetClone;
},
});
}
if (oldModel.autoMigrateFrom) {