chore: migrate to pnpm and fix default value resolution for coercion schemas#21
Merged
Conversation
This file contains hidden or 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
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.
packageManagerin
package.json, replacespackage-lock.jsonwithpnpm-lock.yaml, andupdates all three GitHub Actions workflows (
ci.yml,publish.yml,bump-version.yml) to usepnpm/action-setup@v4with pinned SHAsdefaultnot appearing in generated markdown for coercion schemas(e.g.
z.stringbool().default(false)): Zod v4 places the default on theoutput JSON schema rather than the input schema for these types
(
{ ...outputSchema, ...inputSchema }), so input takes precedence forconstraints/enum while output fills in gaps for post-coercion fields
generateMarkdownasync and awaitsvalidate()to support asyncStandard Schema implementations; fixes optional detection to use
!issuesper the spec rather than'value' in result