Skip to content

Remove Tags feature from frontend, keep backend Tag API intact - #73

Closed
evertonschuster wants to merge 1 commit into
pr/03-catalog-category-foundationfrom
pr/04-remove-tags-frontend
Closed

Remove Tags feature from frontend, keep backend Tag API intact#73
evertonschuster wants to merge 1 commit into
pr/03-catalog-category-foundationfrom
pr/04-remove-tags-frontend

Conversation

@evertonschuster

Copy link
Copy Markdown
Owner

Summary

Split out of #69 (part 4 of 4 — the final piece; see that PR for the full picture). Stacked on #72 (Catalog Result migration + physical reorg) — this PR's base is #72's branch, so the diff shown here is only what this PR adds.

Removes the entire Tags vertical from apps/admin-frontend (domain, application, infrastructure, presentation, MSW handlers, E2E specs, nav entry, route, and catalog facade wiring) while intentionally retaining the backend Tag domain entity and /api/v1/tags endpoints, including Service's many-to-many relationship to Tag — a project-owner decision, see docs/adr/016-remove-tags-frontend.md. Categories replaces Tags as the reference CRUD implementation throughout the docs and the agenza-frontend-feature skill.

This is the same content as the standalone Tags-removal work already verified earlier this session against the full 246-file branch tip — reapplied here on top of the split stack (#70/#71/#72) instead of as one monolithic PR.

Test plan

  • npm install + npm run build --workspace=apps/admin-frontend — green
  • npm run lint --workspace=apps/admin-frontend — clean, 0 warnings
  • npm run format:check --workspace=apps/admin-frontend — clean
  • npm run test --workspace=apps/admin-frontend — 305/305 passing
  • scripts/sync_agent_skills.py --check, scripts/check_agent_governance.py, scripts/architecture_guard.py — all pass

🤖 Generated with Claude Code

Split out of #69 (part 4 of 4 — see that PR for the full picture).
Stacked on #72 (Catalog Result migration + physical reorg).

Removes the entire Tags vertical from apps/admin-frontend (domain,
application, infrastructure, presentation, MSW handlers, E2E specs, nav
entry, route, and catalog facade wiring) while intentionally retaining
the backend Tag domain entity and /api/v1/tags endpoints, including
Service's many-to-many relationship to Tag - a project-owner decision,
see docs/adr/016-remove-tags-frontend.md. Categories replaces Tags as
the reference CRUD implementation throughout the docs and the
agenza-frontend-feature skill.

This is the same content as the standalone Tags-removal commit already
verified earlier against the full 246-file branch tip - reapplied here
on top of the split stack (#70/#71/#72) instead.

## Test plan

- [x] `npm install` + `npm run build --workspace=apps/admin-frontend` — green
- [x] `npm run lint --workspace=apps/admin-frontend` — clean, 0 warnings
- [x] `npm run format:check --workspace=apps/admin-frontend` — clean
- [x] `npm run test --workspace=apps/admin-frontend` — 305/305 passing
- [x] `scripts/sync_agent_skills.py --check`, `scripts/check_agent_governance.py`, `scripts/architecture_guard.py` — all pass

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 2, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dc182dd0-f4f3-455a-bac3-ceafcdb7f574

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@evertonschuster

Copy link
Copy Markdown
Owner Author

Fechando em favor de uma nova PR — essa estava baseada na branch antiga da #72 (não mergeada, substituída pela #75). Vou recriar com o mesmo conteúdo a partir do main atualizado.

@evertonschuster

Copy link
Copy Markdown
Owner Author

Recriada como #76 a partir do main atualizado (agora com #70/#71/#75 mergeadas) — mesmo conteúdo, sem mudança funcional.

evertonschuster added a commit that referenced this pull request Aug 2, 2026
Split out of #69 (final part of this series — see that PR for the full
picture). Recreated from origin/main after #70/#71/#75 merged, since
this repo's convention (and the split-large-coderabbit-pr skill) is a
sequential series, not stacking on an unmerged branch. Same content as
the original #73, just re-based; no functional change.

Removes the entire Tags vertical from apps/admin-frontend (domain,
application, infrastructure, presentation, MSW handlers, E2E specs, nav
entry, route, and catalog facade wiring) while intentionally retaining
the backend Tag domain entity and /api/v1/tags endpoints, including
Service's many-to-many relationship to Tag - a project-owner decision,
see docs/adr/016-remove-tags-frontend.md. Categories replaces Tags as
the reference CRUD implementation throughout the docs and the
agenza-frontend-feature skill.

## Test plan

- [x] `npm install` + `npm run build --workspace=apps/admin-frontend` — green
- [x] `npm run lint --workspace=apps/admin-frontend` — clean, 0 warnings
- [x] `npm run format:check --workspace=apps/admin-frontend` — clean
- [x] `npm run test --workspace=apps/admin-frontend` — 305/305 passing
- [x] `npx playwright test` (full e2e suite, production build + preview) — 8/8 passing
- [x] `scripts/sync_agent_skills.py --check`, `scripts/check_agent_governance.py`, `scripts/architecture_guard.py` — all pass

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
@evertonschuster
evertonschuster deleted the pr/04-remove-tags-frontend branch August 2, 2026 15:26
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