feat(api): tag operations for client codegen grouping#1
Merged
Conversation
Add tags = ["Health" | "Catalog" | "Validation" | "Decks"] to every #[utoipa::path] and declare matching tag descriptions on ApiDoc. The tags drive operation grouping in generated clients (e.g. namespaced sub-clients in TS, separate protocols in Swift). Without them the generators emit a single flat client. Document the consumer-side codegen flow in .claude/rules/api-contract.md: each consumer pins a backend SHA in .api-version, fetches openapi.json from raw.githubusercontent.com at that SHA, and commits the generated artifact. The backend publishes no typed packages of its own.
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
2 participants
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.
Add tags = ["Health" | "Catalog" | "Validation" | "Decks"] to every
#[utoipa::path] and declare matching tag descriptions on ApiDoc. The
tags drive operation grouping in generated clients (e.g. namespaced
sub-clients in TS, separate protocols in Swift). Without them the
generators emit a single flat client.
Document the consumer-side codegen flow in .claude/rules/api-contract.md:
each consumer pins a backend SHA in .api-version, fetches openapi.json
from raw.githubusercontent.com at that SHA, and commits the generated
artifact. The backend publishes no typed packages of its own.