Fix action form parsing for .nullish #11452
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: aa885e0 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
bot
added
the
pkg: astro
bluwy
approved these changes
Jul 17, 2024
bholmesdev
approved these changes
Jul 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
In the experimental Astro actions, users can provide an input schema using zod and parse formdata natively with
accept: 'form'. However, if a user uses the.nullish()zod modifier, it will always treat the field as a string, regardless of the intended type.This is because zod's
.nullish()is equivalent to.nullable().optional()and returnsz.ZodOptional<z.ZodNullable<ActualType>>and must be double-unwrapped to get the underlying type.This change swaps from a single-unwrap of
ZodOptionalandZodNullableto a loop that can go as deep as needed.Testing
This change was not tested.
Docs
No docs were written or changed as this is a bugfix.