[web] Tickets and Clients as first-class workspace views - #103
Merged
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
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.
The workspace treated the queue as the default and the clients page as an overlay: the topbar "clients" button only ever turned the view on, so once on the clients page there was no way back to tickets from the topbar (only the close button in the page header).
Turn Tickets and Clients into peer, first-class views:
viewstate ('tickets' | 'clients') instead of toggling a boolean.No change to the content of either view — only how they're switched. This is the first step toward the larger nav revision (left-rail consolidation, issue #95).
Closes #102
Authored/Written by: Qwen3.8-27b