Skip to content
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

Update dependency @conform-to/zod to v1.2.2 #119

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 13, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@conform-to/zod (source) 1.1.0 -> 1.2.2 age adoption passing confidence

Release Notes

edmundhung/conform (@​conform-to/zod)

v1.2.2

Compare Source

What's Changed

fix: revert auto field value update (#​778)

Revert https://github.com/edmundhung/conform/pull/729 and https://github.com/edmundhung/conform/pull/766

The auto field value update feature introduced in v1.2.0 has caused several critical issues with significant user impact. While I appreciate what they accomplished, I’ve realized the current solution isn't robust enough to handle all potential use cases. To minimize the impact on everyone, I believe it's best to revert these changes for now.

Full Changelog: edmundhung/conform@v1.2.1...v1.2.2

v1.2.1

Compare Source

What's Changed

  • Fixed an issue with Conform overwriting the value of input buttons in #​766. In v1.2.0, if you have any input buttons rendered, their value will be likely rewritten to empty string as Conform treats it as normal inputs and tries to update its value based on the default value.

Full Changelog: edmundhung/conform@v1.2.0...v1.2.1

v1.2.0

Compare Source

Embrace the platform

This change is reverted in v1.2.2

One of the most critical changes in this release is the auto field value update implemented in #​729. Conform now updates input value using the DOM api instead of relying on the key to re-mount the inputs with the new defaultValue. It means:

  • It is no longer required to pass the key (e.g. fields.title.key) to the input elements unless you are rendering a list.
// Before: The minimum setup
<input key={field.title.key} name={fields.title.name} defaultValue={fields.title.defaultValue} />
// Now: the key props is no longer required 
<input name={fields.title.name}  defaultValue={fields.title.defaultValue} />
// Bonus: if the form is not rendered server side, or you don't mind the user experience before JS is loaded...
<input name={fields.title.name} />
  • Helpers like getInputProps, getSelectProps or getTextareaProps are no longer spreading a key to the input element. If you were seeing the message Warning: A props object containing a "key" prop is being spread into JSX, it should be resolved now.
  • Outstanding issues caused by inputs being unmounted (e.g. #​701 and #​730) are now fixed

Pre-release

Thanks to pkg.pr.new, we are now releasing a preview version on every pull request (#​742)

You will find a comment on the PR like this one from pkg.pr.new with each package name listed. If you expand the item, you will see a command to install the pre-release version. If you are not using pnpm, you can swap it with npm install, or just copy the package URL and replace the version in the package.json with it.

We are also shipping a pre-release version on every commit merged to main in the format https://pkg.pr.new/@&#8203;conform-to/package@commit . For example, if you would like to install the pre-release version of @conform-to/dom and @conform-to/zod up to db63782, you can run:

npm install https://pkg.pr.new/@&#8203;conform-to/dom@db63782
npm install https://pkg.pr.new/@&#8203;conform-to/zod@db63782

Other Improvements

  • Improved the types of submission.payload in #​706. If you were using Remix with single fetch, the action results should no longer be in type never. Thanks @​timvandam!
  • Fixed empty string default value support in #​741. Previously, we suggested using .default() to set a fallback value. However, .default() does not work as expected with z.string().default(''). This issue has now been resolved, but keep in mind that the default value is still subject to validation errors. For more predictable results, we recommend using .transform(value => value ?? defaultValue) instead.
  • Implement zod object coercion in #​733. Conform should support nested fields with only checkboxes now.
  • Added bigint coercion support with zod in #​726. Thanks @​lifeiscontent!
  • Improved the types of the default value in #​719. As FormValue should never be null. Thanks @​aaronadamsCA!
  • Added a multiple select example with shadcn-ui in #​753. Thanks @​pwli0755!
  • Improved the shadcn-ui Switch Component example to use control.value in #​721. Thanks @​reborn2135!
  • Fixed typo in parseWithYup.md and FormProvider.md in #​708, #​751. Thanks @​uttk, @​felixyeboah!
  • Improved the ja docs messages in #​709, #​710, #​711, #​712. Thanks @​k70suK3-k06a7ash1!
  • Explained the usage of allErrors with checkbox group in #​735.

New Contributors

Full Changelog: edmundhung/conform@v1.1.5...v1.2.0

v1.1.5

Compare Source

Improvements

  • Fixed an issue with unstable_useControl not resetting the value of the registered input on form reset (#​674)

Full Changelog: edmundhung/conform@v1.1.4...v1.1.5

v1.1.4

Compare Source

Improvements

New Contributors

Full Changelog: edmundhung/conform@v1.1.3...v1.1.4

v1.1.3

Compare Source

What's Changed
New Contributors

Full Changelog: edmundhung/conform@v1.1.2...v1.1.3

v1.1.2

Compare Source

What's Changed

Full Changelog: edmundhung/conform@v1.1.1...v1.1.2

v1.1.1

Compare Source

What's Changed

Full Changelog: edmundhung/conform@v1.1.0...v1.1.1


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "* 0-3 * * 1" (UTC).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 2a31597 to fc0947f Compare May 13, 2024 03:36
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from fc0947f to de221a1 Compare May 27, 2024 22:28
@renovate renovate bot changed the title Update dependency @conform-to/zod to v1.1.3 Update dependency @conform-to/zod to v1.1.4 May 27, 2024
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 2 times, most recently from cbfddef to 20b6877 Compare June 3, 2024 03:21
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 20b6877 to 8974733 Compare June 17, 2024 22:02
@renovate renovate bot changed the title Update dependency @conform-to/zod to v1.1.4 Update dependency @conform-to/zod to v1.1.5 Jun 17, 2024
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 8974733 to 4daaf5e Compare June 24, 2024 00:10
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 2 times, most recently from 6d52ce6 to 324d76d Compare July 8, 2024 00:48
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 324d76d to 0c3ea9d Compare July 15, 2024 01:58
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 2 times, most recently from 72aa14b to d19d164 Compare August 5, 2024 00:24
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from d19d164 to b145652 Compare August 5, 2024 03:03
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from b145652 to d026991 Compare August 19, 2024 00:25
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from d026991 to 67ccbd9 Compare August 26, 2024 02:18
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 3 times, most recently from 8deb35b to 9266a43 Compare September 13, 2024 21:55
@renovate renovate bot changed the title Update dependency @conform-to/zod to v1.1.5 Update dependency @conform-to/zod to v1.2.0 Sep 13, 2024
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 9266a43 to 1a6d5db Compare September 14, 2024 16:12
@renovate renovate bot changed the title Update dependency @conform-to/zod to v1.2.0 Update dependency @conform-to/zod to v1.2.1 Sep 14, 2024
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 1a6d5db to 8d19a52 Compare September 20, 2024 02:16
@renovate renovate bot changed the title Update dependency @conform-to/zod to v1.2.1 Update dependency @conform-to/zod to v1.2.2 Sep 20, 2024
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 2 times, most recently from 7677d87 to c2b0170 Compare September 23, 2024 03:34
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 2 times, most recently from ead3d91 to df4d0c6 Compare October 7, 2024 03:45
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 2 times, most recently from e2b810e to 23c22ba Compare October 21, 2024 01:07
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 23c22ba to 362f826 Compare November 4, 2024 00:06
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 362f826 to 60c6421 Compare November 11, 2024 00:39
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from 60c6421 to 74c355c Compare November 18, 2024 01:04
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch 3 times, most recently from dd35867 to fb14efb Compare December 2, 2024 03:09
@renovate renovate bot force-pushed the renovate/conform-to-zod-1.x branch from fb14efb to 9760890 Compare December 16, 2024 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants