Fields can be initially empty/undefined

[MiroslavPetrik]

Currently the checkbox, radio or number fields are strict, so they always contain value of boolean, string or number respectively.

Usually, when field is untouched:

• none of radio buttons should be checked
• number field should be empty like text field with empty string instead of displaying 0

Use Cases

• yes/no radio: when the form requires explicit user input, it must start with undefined radio value, so error message forces the user to pick one of options

[MiroslavPetrik]

For empty values we will use undefined as that plays with zod - when zod has undefined value, the required_error message is being used.

Furthermore, builder pattern can be applies for fieldAtom creation, to get better DX on the validation api.

[github-actions]

🎉 This issue has been resolved in version 1.0.0-next.1 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀