feat(account): withdrawal function and start-at-once consent #273
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-web!273
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "feat/withdrawal-function"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
What
Two consumer-law pieces paid checkout needs (2 kap. 10 a § and 15 § lagen 2005:59). Off until
BILLING_API_URLandBILLING_API_TOKENare set, so nothing changes in production on merge.withdrawalDeadline, with the deadline in Swedish time.withdrawal_requestsbefore the billing service is called, so the consumer's exercise of the right is never lost.beginCheckout, which stores the consent with a timestamp incheckout_consentsand passes it to checkout. There is no checkout UI yet, so these are the pieces checkout will call.error.data.reason, never message text.Version 1.13.0.
Migrations
0007(two new tables),0008and0009(one nullable column each). All additive. Not applied anywhere.Verified
Pre-push: prettier, eslint, stylelint, markdownlint, lang-check,
astro check(0 errors), drizzle-kit check, gitleaks, audit, 400 unit tests, build and e2e all pass.Not done: a manual look at the account page with the feature on. That needs a running billing service.
Before release
beginCheckout.Refs #259. It closes once a test-mode withdrawal reaches the billing service end to end.