You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

50 lines
1.9 KiB
Markdown

+++
title = "Implement tag join logic — fetch tags per quote, insert/replace tags on create/update"
priority = 5
status = "todo"
ticket_type = "task"
dependencies = ["a5049d"]
+++
<context>
The `quotesdb` API is built with Axum + Tokio, targeting Cloudflare Workers via `workers-rs`. It serves JSON at `/api/*` endpoints and persists data to Cloudflare D1 (production) or a local SQLite file via Turso (development). Source lives in `src/bin/api/`.
Shared types and utilities are in `src/lib.rs` — code placed there must compile for both the host target and `wasm32-unknown-unknown`.
Each quote can have multiple tags stored in the `quote_tags` join table. Tags are not normalised — they are stored as plain strings per quote. On create/update, all tags for the quote are replaced atomically.
</context>
<goal>
Implement tag fetch and upsert logic used by the API handlers:
1. `fetch_tags_for_quote(pool, quote_id) -> Vec<String>` — SELECT from quote_tags
2. `replace_tags_for_quote(pool, quote_id, tags: &[String])` — DELETE existing, INSERT new tags in a transaction
This logic should live in a `db` or `tags` module and be called from the create and update handlers.
</goal>
<constraints>
- Tag replacement must be atomic (use a transaction).
- Empty `tags` array means "remove all tags" — this is valid.
- Cascade delete on `quote_tags` handles tag cleanup when a quote is deleted — no separate delete-tags step needed.
</constraints>
<skills>
Use `superpowers:test-driven-development` — write unit tests that verify tag insertion, replacement, and empty-tag cases.
Use `superpowers:verification-before-completion` before closing.
</skills>
<validation>
Run in order from the `quotesdb/` directory:
```sh
cargo fmt
cargo check
cargo clippy
cargo test
```
</validation>
<commit>
`feat(quotesdb): implement tag join logic — fetch and replace tags per quote`
</commit>