Move app settings to a gear in the header - #458
Merged
Conversation
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
1 participant
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.
What changed
App settings open from one gear beside the app name in the existing header. The shell no longer adds a Settings tab to app navigation. The gear has an app-specific label, a native tooltip, an active state, and a 44 px phone touch target. Global Settings stays in the sidebar footer.
Closes DRU-465.
Risk
Frontend navigation and CSS only. The gear uses the existing settings route and draft protection. No API or database changes.
Verification
npm --prefix frontend run lint— passed.npm --prefix frontend test— all 390 tests passed. Updated existing assertions.npm --prefix frontend run build— passed.