fix: remove hardcoded split payment amounts #16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "15-fix-split-payment-text"
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?
Summary
Changes
src/routes/contract/[token]/+page.svelte: Updated split payment description on line 319 (travel contract) and line 377 (local contract)Test Plan
npm run buildpasses cleanReview Checklist
Related
Review: Approved
Diff: 1 file, +2/-2. Exactly the two lines specified in #15, no extraneous changes.
Verification:
npm run build-- cleannpm test-- 12/12 passNo findings. Ready to merge.
PR #16 Review
DOMAIN REVIEW
Stack: SvelteKit / Svelte template (HTML content change only)
This is a pure content/copy fix -- two lines of static text inside a
.sveltetemplate. No logic, no bindings, no reactive statements, no CSS, and no server-side code changed.Content correctness:
grepfor "on the 15th" and "on the 30th" returns zero hits. The remaining$100at line 209 is an unrelated gas cost in a trip breakdown table.Accessibility: No accessibility impact -- plain paragraph text, no new interactive elements, no ARIA concerns.
Performance: No bundle impact -- static text change only.
BLOCKERS
None.
This is a two-line static text change. No new functionality is introduced, so the "new functionality must have tests" blocker does not apply. No user input handling, no secrets, no auth paths, no logic changes.
NITS
Apostrophe encoding: The text uses a literal curly apostrophe in "you'd" and "we'll". This renders correctly in browsers but some linters or build tools can flag non-ASCII in source. Not a real problem here -- SvelteKit handles UTF-8 fine -- but worth noting for awareness.
Hardcoded dates still present elsewhere: The payment schedule sections still contain hardcoded dates ("March 27", "April 6", "May 1", "June 18"). These are intentionally specific per the contract terms, but if the business changes dates frequently, extracting them to a config or data layer would reduce future one-off text fixes. This is out of scope for this PR.
SOP COMPLIANCE
15-fix-split-payment-textreferences issue #15PROCESS OBSERVATIONS
VERDICT: APPROVED