Repository navigation
feat(interpolation): Persist dashboard and saved query transformations - #127081
nsdeschenes wants to merge 5 commits into
Conversation
|
bugbot run |
|
This PR has a migration; here is the generated SQL for for --
-- Add field transformations to dashboardwidgetquery
--
ALTER TABLE "sentry_dashboardwidgetquery" ADD COLUMN "transformations" jsonb NULL; |
|
This PR has a migration; here is the generated SQL for for --
-- Add field transformations to dashboardwidgetquery
--
ALTER TABLE "sentry_dashboardwidgetquery" ADD COLUMN "transformations" jsonb NULL; |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9652247. Configure here.

The goal of this PR is to enables users to create and save dashboards and queries utilizing transformation functions.
🤖 generated description below:
Why
Dashboard and saved Explore query APIs need to retain per-axis transformations using the positional contract in #127057. Save the ordered function strings as opaque metadata so query execution can interpret them separately.
What changed
yAxespositions.Scope
Backend persistence and API round trips. Frontend propagation and transformation execution remain follow-ups.
Blast Radius
Nonempty writes require
explore-interpolation-and-smoothing. Dashboard updates retain omitted maps, and{}clears them. With the flag disabled, nonempty saves and transformed revision restores are rejected. Stored maps remain readable.Verification