Skip to content

VI-5068 Move the TAMS version badge under the active store name - #21

Merged
helgehoi merged 1 commit into
mainfrom
VI-5068-version-badge-under-store-name
Aug 26, 2026
Merged

helgehoi merged 1 commit into
mainfrom
VI-5068-version-badge-under-store-name

Conversation

@helgehoi

Copy link
Copy Markdown
Collaborator

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 info badge 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.

 before                        after
┌─────────────────────┐      ┌─────────────────────┐
│ my-tams-store       │      │ my-tams-store       │
├─────────────────────┤      ├─────────────────────┤
│ Sources             │      │ [TAMS 8.2]          │
│ Flows               │      │                     │
│ Profiles            │      │ Sources             │
│ Webhooks            │      │ Flows               │
│ ─────────────────── │      │ Profiles            │
│ Manage Stores  [8.2]│      │ Webhooks            │
└─────────────────────┘      │ ─────────────────── │
                             │ Manage Stores       │
                             └─────────────────────┘

How

Cloudscape's SideNavigation has no header subtitle, and header.text is typed string and rendered inside the header's <a> — putting a badge there would fold "TAMS 8.2" into that link's accessible name. Instead this uses itemsControl, 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 /service could 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 build passes (Node 22, same as CI)
  • Ran locally via npm run dev and checked the sidebar
  • npm run lint still 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

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>
@helgehoi
helgehoi merged commit 301c28d into main Aug 26, 2026
1 check passed
@helgehoi
helgehoi deleted the VI-5068-version-badge-under-store-name branch August 27, 2026 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant