chore: version packages - #45
Merged
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@zipbul/baker@6.0.0
Major Changes
e72460c: Compile-time rule↔field type checking, richer issues, and a leaner published surface.
@Fieldis now type-checked (breaking). A rule applied to a field of the wrong type is a compile error —@Field(isString) age!: numberand@Field(isString, min(5)) code!: stringno longer typecheck. Correctly typed DTOs are unaffected; runtime behaviour is identical. Dynamic/untyped rule lists remain available via@Field({ rules: [...] }).BakerIssue.constraintsnow carries the failing rule's parameters (e.g.{ min: 5 }formin(5)), so you can build error messages without re-deriving bounds. Type-check rules and structural failures omit it..d.ts.