Skip to content

feat!: adopt phoxal 0.9 domain-first contract enums#21

Merged
jBernavaPrah merged 1 commit into
mainfrom
chore/phoxal-0.9
Jun 15, 2026
Merged

feat!: adopt phoxal 0.9 domain-first contract enums#21
jBernavaPrah merged 1 commit into
mainfrom
chore/phoxal-0.9

Conversation

@jBernavaPrah

Copy link
Copy Markdown
Contributor

Bumps phoxal 0.6 → 0.9.0 and migrates the operator to the domain-first contract enums (phoxal#69).

  • Topics use topic::new().<domain>() (no .v1()); old phoxal::api::v1 imports removed.
  • Subscription payloads are contract enums, unwrapped through exhaustive V1 matches (no catch-all — a future variant fails to compile).
  • Asset queries wrap GetRequest::V1(..) and match GetResponse::V1(..).
  • Rendering/logging/event code keeps the inner v1 structs after unwrap.

Verified (independent, offline against published 0.9): cargo build/test/clippy --workspace --all-features green (17 tests); zero leftover api::v1/.v1() refs. Codex cross-review: no findings. Mechanical type/shape migration — behavior unchanged.

🤖 Generated with Claude Code

Bump phoxal 0.6→0.9 and migrate the operator to the domain-first API: topics use
`topic::new().<domain>()` (no `.v1()`), subscription payloads are contract enums
unwrapped through exhaustive `V1` matches (no catch-all), and asset queries wrap
`GetRequest::V1(..)` / match `GetResponse::V1(..)`. Rendering/logging keep the
inner v1 structs after unwrap; behavior unchanged.

Verified: cargo build/test/clippy --workspace --all-features green (17 tests).

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@jBernavaPrah jBernavaPrah merged commit 7e7a5be into main Jun 15, 2026
4 checks passed
@jBernavaPrah jBernavaPrah deleted the chore/phoxal-0.9 branch June 15, 2026 20:07
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