chore(ui): remove the imagery adjustment panel from View Results - #180
Open
Caleb Robinson (calebrob6) wants to merge 1 commit into
Open
chore(ui): remove the imagery adjustment panel from View Results#180Caleb Robinson (calebrob6) wants to merge 1 commit into
Caleb Robinson (calebrob6) wants to merge 1 commit into
Conversation
The opacity, contrast, hue rotation and saturation sliders are gone from the results page, along with the state and the two handlers that existed only to feed them. The panel wrote straight to the Azure Maps layer options and its reset button restored opacity 1, contrast 0, hueRotation 0, saturation 0, which are the values the layers already start with. Removing it therefore changes nothing about what the map draws. The labeling tool has its own separate copy of these sliders in LabelingToolLeftPanel, which is untouched. The shared .labeling-imagery-controls CSS class stays for that reason.
Copilot started reviewing on behalf of
Caleb Robinson (calebrob6)
August 31, 2026 21:34
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the imagery adjustment controls from View Results without affecting the labeling tool.
Changes:
- Deletes the imagery controls component.
- Removes its state, handlers, import, and rendering.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
VisualizerImageryControls.jsx |
Removes the obsolete controls component. |
Visualizer.jsx |
Removes associated wiring and state. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the opacity, contrast, hue rotation and saturation sliders from the View Results page, along with the state and the two handlers that only existed to feed them.
Split out of #136, which is where the request came from, so it can be reviewed on its own.
Why this is safe
The panel wrote straight to the Azure Maps layer options, and its reset button restored
opacity: 1, contrast: 0, hueRotation: 0, saturation: 0. Those are the values the layers already start with, so removing the panel changes nothing about what the map draws.getLayerByIdstays; it has other callers.What is not touched
The labeling tool has its own separate copy of these sliders in
LabelingToolLeftPanel.jsx. That is unaffected, which is also why the shared.labeling-imagery-controlsCSS class stays.Verification
209 deletions, no additions.
node --test)vite buildmainmeasured in the same containerVisualizer.jsxNo browser check. This repo has no Playwright config, so the page was verified by build and lint rather than by loading it.