MRKT-161: ensures numeric input values stored in formik as numbers #758
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 106ac23. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
|
Visit the studio preview URL for this PR 🚀 : https://758.artist.preview.newm.io/ |
|
Visit the tools preview URL for this PR (updated for commit 6ef20ac): |
|
Visit the wallet preview URL for this PR (updated for commit 6ef20ac): |
|
Visit the marketplace preview URL for this PR (updated for commit 6ef20ac): |
| ref={ ref } | ||
| { ...field } | ||
| { ...props } | ||
| onChange={ handleChange } |
There was a problem hiding this comment.
If an onchange is passed I believe this will override that. Do we have instances with an onchange/handle change we need to account for?
There was a problem hiding this comment.
There shouldn't be any use case where onChange would be passed to a Formik field. For inputs where an onChange prop is passed, the non-Formik component can be used.
No description provided.