-
Notifications
You must be signed in to change notification settings - Fork 475
use new select component, enable multiselect / multi-group #9420
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.
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
Conversation
|
Vadman97
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense to me
…#9420) ## Summary - switch the graphing editor / variable comboboxes over to use the new select component - fix some styling with the select component, add a loading spinner while fetching results - change graph `groupByKeys` and variable `defaultValues` to support multiple values <!-- Ideally, there is an attached GitHub issue that will describe the "why". If relevant, use this section to call out any additional information you'd like to _highlight_ to the reviewer. --> ## How did you test this change? - clicktested locally <!-- Frontend - Leave a screencast or a screenshot to visually describe the changes. --> ## Are there any deployment considerations? - defaultValues change is backwards compatible with existing format - groupByKeys change needs a migration - will run this directly after automigrate: ``` update graphs set group_by_keys = ARRAY[group_by_key] where group_by_key is not null ``` (until this migration runs, existing graphs using group by will lose their grouping) <!-- Backend - Do we need to consider migrations or backfilling data? --> ## Does this work require review from our design team? - @julian-highlight fyi <!-- Request review from julian-highlight / our design team -->
Summary
groupByKeysand variabledefaultValuesto support multiple valuesHow did you test this change?
Are there any deployment considerations?
(until this migration runs, existing graphs using group by will lose their grouping)
Does this work require review from our design team?