Verify Zod schema validation for FederalTaxInput at HTTP boundaries #243
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Confirmed that Zod schema validation has been properly implemented to address CodeRabbit's security review feedback on PR #238.
Validation Implementation
Schema Definition:
FederalTaxInputSchemaintax-formulas.ts(lines 520-537)year(2018-2025),filingStatus(enum),wages(non-negative)Boundary Validation: Applied in
http-bridge.tsat both endpoints/api/forecast/tax(lines 1059-1071)/api/forecast/tax/pdf(lines 1100-1112)safeParse()with 400 error responses on invalid inputcalculateFederal()Notes
The
ForecastHttpRequestSchemastill usesz.any()for initial parsing to avoid circular dependencies, but strict validation occurs in the handler before calculation functions are called. This pattern satisfies the security requirement of validating all user inputs at API boundaries.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.