Skip to content

Conversation

Zylphrex
Copy link
Member

Previously, explore supported multiple y axis per chart, so each visualize supported multiple y axis. That functionality has since been removed for simplicity so update the types here to match. Keep in mind that saved queries still store them as an array so when serializing/deserializing, we still need to treat it as an array.

Previously, explore supported multiple y axis per chart, so each visualize
supported multiple y axis. That functionality has since been removed for
simplicity so update the types here to match. Keep in mind that saved queries
still store them as an array so when serializing/deserializing, we still need to
treat it as an array.
@Zylphrex Zylphrex requested a review from a team as a code owner June 20, 2025 15:45
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 20, 2025
Copy link
Member

@shruthilayaj shruthilayaj left a comment

Choose a reason for hiding this comment

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

tested it out locally, looks good

@Zylphrex Zylphrex merged commit c05a0c6 into master Jun 20, 2025
44 checks passed
@Zylphrex Zylphrex deleted the txiao/ref/visualize-should-only-have-1-yaxis branch June 20, 2025 19:36
@github-actions github-actions bot locked and limited conversation to collaborators Jul 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants