Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dataplane: Deprecate timeseries-many in favor of timeseries-multi #59070

Merged
merged 5 commits into from
Dec 1, 2022
Merged

Dataplane: Deprecate timeseries-many in favor of timeseries-multi #59070

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
87bcf6c
deprecate timeseries-many in favor of timeseries-multi
bohandley Nov 21, 2022
3b6603f
deprecate timeseries-many, do not just remove it
bohandley Nov 21, 2022
ae936eb
undo changes to jsonc files
bohandley Nov 28, 2022
0924862
update deprecation message
bohandley Nov 28, 2022
0d85c1b
return TimeSeriesMulti for prepareTimeSeries transformer
bohandley Dec 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions packages/grafana-data/src/types/dataFrameTypes.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,12 @@
export enum DataFrameType {
TimeSeriesWide = 'timeseries-wide',
TimeSeriesLong = 'timeseries-long',

/** @deprecated in favor of TimeSeriesMulti */
TimeSeriesMany = 'timeseries-many',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a breaking change in our public (typescript) API?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good question! @kylebrandt @ryantxu Is this supposed to be a breaking change or not? We need to consider the typescript API as Josh mentioned.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is and isn't a breaking changes for plugins is tricky to define for the frontend. Typescript is not a runtime concern, so this will not break any existing plugins from running. But it could prevent them from being built.

From the outside, a simple way out would be to actually deprecate (rather than remove) the enum value with @deprecated jsdoc annotation, and then remove in grafana 10.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly what @joshhunt said - https://github.com/grafana/grafana/blob/main/contribute/breaking-changes-guide.md#deprecate-first

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup deprecating not removing

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add something to point to the replacement, e.g. "use TimeSeriesMulti instead", or "@deprecated in favor of TimeSeriesMulti"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the text @kylebrandt


TimeSeriesMulti = 'timeseries-multi',

/** Directory listing */
DirectoryListing = 'directory-listing',

Expand Down