fix(contractor-onboarding) - pass employment_id to contract details to get the right schema#736
fix(contractor-onboarding) - pass employment_id to contract details to get the right schema#736gabrielseco wants to merge 3 commits intomainfrom
Conversation
📦 Bundle Size Report
Size Limits
Largest Files (Top 5)
View All Files (283 total)
✅ Bundle size check passed |
|
Deploy preview for remote-flows ready! ✅ Preview Built with commit 95f73c0. |
|
Deploy preview for remote-flows-example-app ready! ✅ Preview Built with commit 95f73c0. |
|
npm warn exec The following package was not found and will be installed: tsx@4.21.0 📊 Coverage Report⚪ Coverage unchanged
Detailed BreakdownLines Coverage
Statements Coverage
Functions Coverage
Branches Coverage
✅ Coverage check passed |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
For COR we have a different contract_details schema, that's. why we need to pass the employment_id
Note
Low Risk
Small, localized change to schema-fetching parameters and query caching; primary risk is unintended cache misses or backend rejecting the new optional query parameter.
Overview
Contractor onboarding now includes the current
employment_idwhen fetching the contractorcontract_detailsJSON schema, and keys the React Query cache by bothcountryCodeandemploymentIdto avoid reusing the wrong schema across employments.The generated API types are updated to allow
employment_idas an optional query param forgetShowContractorContractDetailsCountry, and SDK docs/security metadata forgetShowFormCountryare refreshed (auto-generated changes).Written by Cursor Bugbot for commit 95f73c0. This will update automatically on new commits. Configure here.