the view is there under number 5, the sidebar is there, but the main area is not showing anything, because it is not wired yet. needs to be wired up and implemented just like in the GUI app.
the view is there under number 5, the sidebar is there, but the main area is not showing anything, because it is not wired yet. needs to be wired up and implemented just like in the GUI app.
hugo
added the idea label 2026-07-16 20:24:26 +00:00
Implemented in 2fd132e — the tags view (key 5) main area is now wired up, mirroring the GUI tags editor.
What was built
New renderer-agnostic core BDS.UI.TagsPanel carrying the same BDS.Tags operations the GUI tags editor uses (create, rename, colour presets, post template, delete, merge, sync-from-posts) with localized result messages. The GUI editor now sources its colour presets and tag counts from this module, so both frontends cannot drift.
The three sidebar entries open their section in the main area:
Tag Cloud — tags with post usage counts, ordered by usage.
Create / Edit — alphabetical list; n new-tag prompt, enter rename prompt (status-line prompts like the settings forms), c cycles the colour through the shared presets, t cycles the post template, d → y deletes with a post-count confirmation (any other key cancels), s syncs tags from post tags.
Merge Tags — space marks tags, m merges the marked tags into the selected one (same ≥2-tags + target rule as the GUI).
Domain tag events reload an open panel, so changes from the GUI or the CLI show up live.
Spec: specs/tui.allium gained the TagsPanel rule (validated with allium check); UI strings are gettext'd with de/fr/it/es translations.
Verification: 7 new TUI tests covering all three sections (open, create, rename, colour cycle, confirmed/cancelled delete, merge, sync); full suite 1455 passed / 0 failed, credo --strict clean, deps.audit clean, dialyzer 0 errors.
Implemented in 2fd132e — the tags view (key 5) main area is now wired up, mirroring the GUI tags editor.
**What was built**
- New renderer-agnostic core `BDS.UI.TagsPanel` carrying the same `BDS.Tags` operations the GUI tags editor uses (create, rename, colour presets, post template, delete, merge, sync-from-posts) with localized result messages. The GUI editor now sources its colour presets and tag counts from this module, so both frontends cannot drift.
- The three sidebar entries open their section in the main area:
- **Tag Cloud** — tags with post usage counts, ordered by usage.
- **Create / Edit** — alphabetical list; `n` new-tag prompt, `enter` rename prompt (status-line prompts like the settings forms), `c` cycles the colour through the shared presets, `t` cycles the post template, `d` → `y` deletes with a post-count confirmation (any other key cancels), `s` syncs tags from post tags.
- **Merge Tags** — `space` marks tags, `m` merges the marked tags into the selected one (same ≥2-tags + target rule as the GUI).
- Domain tag events reload an open panel, so changes from the GUI or the CLI show up live.
- Spec: `specs/tui.allium` gained the `TagsPanel` rule (validated with `allium check`); UI strings are gettext'd with de/fr/it/es translations.
**Verification**: 7 new TUI tests covering all three sections (open, create, rename, colour cycle, confirmed/cancelled delete, merge, sync); full suite 1455 passed / 0 failed, credo --strict clean, deps.audit clean, dialyzer 0 errors.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
the view is there under number 5, the sidebar is there, but the main area is not showing anything, because it is not wired yet. needs to be wired up and implemented just like in the GUI app.
Implemented in
2fd132e— the tags view (key 5) main area is now wired up, mirroring the GUI tags editor.What was built
BDS.UI.TagsPanelcarrying the sameBDS.Tagsoperations the GUI tags editor uses (create, rename, colour presets, post template, delete, merge, sync-from-posts) with localized result messages. The GUI editor now sources its colour presets and tag counts from this module, so both frontends cannot drift.nnew-tag prompt,enterrename prompt (status-line prompts like the settings forms),ccycles the colour through the shared presets,tcycles the post template,d→ydeletes with a post-count confirmation (any other key cancels),ssyncs tags from post tags.spacemarks tags,mmerges the marked tags into the selected one (same ≥2-tags + target rule as the GUI).specs/tui.alliumgained theTagsPanelrule (validated withallium check); UI strings are gettext'd with de/fr/it/es translations.Verification: 7 new TUI tests covering all three sections (open, create, rename, colour cycle, confirmed/cancelled delete, merge, sync); full suite 1455 passed / 0 failed, credo --strict clean, deps.audit clean, dialyzer 0 errors.