feat(stripe): dunite-stripe crate with shared Stripe response DTOs (DEV-515 pt 1) #29
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/DEV-515-dunite-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 (full Stripe service extraction, under the DEV-495 epic), sequenced small to keep a billing-critical refactor reviewable. Adds
dunite-stripeholding the async-stripe response DTOs - product / price / subscription / subscription-item / checkout-price / invoice / webhook-endpoint - shared verbatim by a8n-tools and bunyip. Pure serde structs, zero coupling.Next slice (follow-up PR)
The async-stripe
StripeService+ the runtimeStripeConfig, behind a neutralStripeServiceErroreach consumer maps to its ownAppError(the ~49-site error neutralization), plus its own async-stripe + reqwest 0.12 deps. Secret storage/encryption, the DB config model, tier reconciliation, and admin presentation stay per-consumer.Tests
cargo build,cargo clippy --all-targets -- -D warnings,cargo fmt --checkclean. Pure structs, no logic to unit-test here.🤖 Generated with Claude Code
https://claude.ai/code/session_01QLd9c7niucrqx68v4AxVss