Repository navigation
VI-5068 Move the TAMS version badge under the active store name - #21
Merged
Merged
Conversation
The detected version sat as an info badge on the Manage Stores nav item, at the bottom of the sidebar and far from the store it describes. It now renders in SideNavigation's itemsControl slot -- directly below the store name in the nav header, on its own line -- so the version reads as a property of the active store rather than of the Manage Stores link. Colour logic is unchanged: blue with a version, grey for a store advertising none, red when /service could not be reached. It still renders only once capability detection has resolved for an active store. README and the Home page are updated to describe the new position. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Ticket
VI-5068 — [tamstool] Upgrade TAMS Store Browser to TAMS 8.2
Follow-up polish on the 8.2 release, which shipped in #20.
Summary
The detected TAMS version sat as an
infobadge on the Manage Stores nav item — at the bottom of the sidebar, below a divider, far from the store it actually describes. It now renders directly below the active store name in the nav header, on its own line.How
Cloudscape's
SideNavigationhas no header subtitle, andheader.textis typedstringand rendered inside the header's<a>— putting a badge there would fold "TAMS 8.2" into that link's accessible name. Instead this usesitemsControl, the component's documented slot "below the header and above the items", which already carries the correct 20px inline padding and top margin. The badge therefore sits just under Cloudscape's header rule rather than tucked against the name.Nothing else changes: colour logic is the same (blue with a version, grey for a store that advertises none, red when
/servicecould not be reached), and it still renders only once capability detection has resolved for an active store. The version shown in the store list is untouched.README and the Home page are updated to describe the new position.
Testing
npm run buildpasses (Node 22, same as CI)npm run devand checked the sidebarnpm run lintstill cannot run in this repo (ESLint 9 needs a flat config, which VI-5068 Support TAMS 8.2 in the TAMS Store Browser #20 left out deliberately) — the build is the gate🤖 Generated with Claude Code