You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somewhat parallel request to #492, refactoring state management. This is a lower-hanging-fruit version of it!
Currently there are a lot of loose state variables that are being passed around the viewer, which makes props for certain components (like CanvasWrapper) very large and unwieldy:
Use Case
Somewhat parallel request to #492, refactoring state management. This is a lower-hanging-fruit version of it!
Currently there are a lot of loose state variables that are being passed around the viewer, which makes props for certain components (like
CanvasWrapper
) very large and unwieldy:Some state could be grouped into objects, the way
config
,scatterPlotConfig
, andvectorConfig
are grouped.Acceptance Criteria
Group related state together and pass into objects, updating their prop APIs:
datasetState
=>collection + dataset + datasetKey
visualizationState
=>featureKey + selectedBackdropKey + colorRamp + colorRampMin + colorRampMax + categoricalColors + selectedTrack + inRangeLUT
Types should be defined for each of these state objects in a
types.ts
file outside ofViewer.tsx
.Details
Please provide any helpful specifications
The text was updated successfully, but these errors were encountered: