-
Notifications
You must be signed in to change notification settings - Fork 619
fix: defaultChainId should be validated in refine
#5638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Your org has enabled the Graphite merge queue for merging into mainAdd the label “merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
Merge activity
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5638 +/- ##
=======================================
Coverage 47.82% 47.82%
=======================================
Files 1088 1088
Lines 56661 56661
Branches 4305 4305
=======================================
Hits 27099 27099
Misses 28864 28864
Partials 698 698
*This pull request uses carry forward flags. Click here to find out more. |
size-limit report 📦
|
https://linear.app/thirdweb/issue/DASH-546/can-not-update-ecosystem-settings-form-if-default-chain-id-is-not-set <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on improving the `update-partner-modal.client.tsx` and `auth-options-form.client.tsx` components by modifying the `DialogTrigger` and enhancing validation logic for the `defaultChainId` field. ### Detailed summary - Changed `DialogTrigger` to use `asChild` prop in `update-partner-modal.client.tsx`. - Made `defaultChainId` optional and adjusted its validation error handling in `auth-options-form.client.tsx`. - Added a new refinement rule to validate `defaultChainId` based on `useSmartAccount`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
ce66e9b to
2c43c64
Compare
https://linear.app/thirdweb/issue/DASH-546/can-not-update-ecosystem-settings-form-if-default-chain-id-is-not-set <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on enhancing the `update-partner-modal.client.tsx` and `auth-options-form.client.tsx` components. It modifies the dialog trigger and updates the validation logic for the form, ensuring better handling of the `defaultChainId` field. ### Detailed summary - Updated `<DialogTrigger>` in `update-partner-modal.client.tsx` to use `asChild`. - Modified `defaultChainId` in `auth-options-form.client.tsx` to be optional. - Added a refinement check to validate `defaultChainId` based on `useSmartAccount` in `auth-options-form.client.tsx`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
2c43c64 to
5a2cfef
Compare
https://linear.app/thirdweb/issue/DASH-546/can-not-update-ecosystem-settings-form-if-default-chain-id-is-not-set
PR-Codex overview
This PR primarily focuses on enhancing the validation logic in the
AuthOptionsFormcomponent and making a minor adjustment to theDialogTriggerin theupdate-partner-modal.client.tsx.Detailed summary
DialogTriggerto useasChildprop inupdate-partner-modal.client.tsx.defaultChainIdto be optional inauth-options-form.client.tsx.defaultChainIdbased onuseSmartAccountinauth-options-form.client.tsx.