chore(deps): update dependency ts-pattern to v5.5.0 #60
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 contains the following updates:
5.0.8
->5.5.0
Release Notes
gvergnaud/ts-pattern (ts-pattern)
v5.5.0
Compare Source
What's Changed
New Contributors
Full Changelog: gvergnaud/ts-pattern@v5.4.0...v5.5.0
v5.4.0
Compare Source
The main thing — Faster type checking 🚀
This release brings a significant perf improvement to exhaustiveness checking, which led to a ~16% decrease in the time to type-check the full test suite of TS-Pattern:
What's Changed
InvertPatternForExcludeInternal
to work with readonly array by @changwoolab in https://github.com/gvergnaud/ts-pattern/pull/284New Contributors
Full Changelog: gvergnaud/ts-pattern@v5.3.1...v5.4.0
v5.3.1
Compare Source
Pattern-matching on symbol keys
Symbols used to be ignored in object patterns. They are now taken into account:
.exhaustive
now throws a custom errorPeople have expressed the need to differentiate runtime errors that
.exhaustive()
might throw when the input is of an unexpected type from other runtime errors that could have happened in the same match expression. It's now possible witherr instanceof NonExhaustiveError
:What's Changed
ExhaustiveError
when no matched pattern by @adamhamlin in https://github.com/gvergnaud/ts-pattern/pull/270New Contributors
Full Changelog: gvergnaud/ts-pattern@v5.2.0...v5.3.1
v5.3.0
Compare Source
v5.2.0
Compare Source
The main thing
new
P.string.length(n)
patternP.string.length(len)
matches strings with exactlylen
characters.What's Changed
P.when
patterns code example by @grigorischristainas in https://github.com/gvergnaud/ts-pattern/pull/260New Contributors
Full Changelog: gvergnaud/ts-pattern@v5.1.2...v5.2.0
v5.1.2
Compare Source
The main thing
When combining
P.nonNullable
andP.nullish
, you should get an exhaustive pattern matching expression, but the following case was incorrectly considered non-exhaustive:This is fixed now.
What's Changed
New Contributors
Full Changelog: gvergnaud/ts-pattern@v5.1.1...v5.1.2
v5.1.1
Compare Source
What's Changed
Full Changelog: gvergnaud/ts-pattern@v5.1.0...v5.1.1
v5.1.0
Compare Source
New features
P.nonNullable
wildcardAdd a new
P.nonNullable
pattern that will match any value exceptnull
orundefined
.Closes #60 #154 #190 and will be a work-around for #143.
What's Changed
Full Changelog: gvergnaud/ts-pattern@v5.0.8...v5.1.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.