refactor(stripe): consume dunite-stripe response DTOs (DEV-515 pt 1) #447
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/DEV-515-consume-stripe-dtos"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
First slice of DEV-515 (under the DEV-495 epic): consume the shared
dunite-striperesponse DTOs, replacing bunyip's local copies. models/stripe.rs re-exports the seven DTOs from the crate so everycrate::models::stripe::*/crate::models::*path is unchanged. The DBStripeConfigmodel, secret encryption helpers, andStripeConfigResponsestay here (app-specific).Next slice (follow-up)
The async-stripe
StripeService(35 methods, 1642 LOC) + the runtimeStripeConfig, behind a neutralStripeServiceError. a8n-tools adoption is separate (with its DTO-field reconciliation).Testing
cargo build -p bunyip-domain -p bunyip-apiclean; clippy + fmt clean; the 17 retained encryption / masking / config unit tests pass. Depends on dunite PR #29.🤖 Generated with Claude Code
https://claude.ai/code/session_01QLd9c7niucrqx68v4AxVss