v.1.9.0 #192
Open
v.1.9.0 #192
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
This was
linked to
issues
Sep 20, 2025
feat: use Standard Schema `~standard` property on any nested schema property feat: `useRules` for a stateless and functionnal use of Regle feat: `forceValues` parameter in `$validate` method. Patch the state before validating BREAKING CHANGE: `flatErrors` now follow standard Issue format, `path` is now Array (ex: `path: "foo.0.bar"` -> `path: ["foo", 0, "bar"]`
victorgarciaesgi
force-pushed
the
next
branch
from
a9b45f8 to
a30849e
Compare
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.
feat: use Standard Schema
~standardproperty on any nested schema propertyfeat:
useRulesfor a stateless and functionnal use of Reglefeat:
forceValuesparameter in$validatemethod. Patch the state before validatingBREAKING CHANGE:
flatErrorsnow follow standard Issue format,pathis now Array (ex:path: "foo.0.bar"->path: ["foo", 0, "bar"]