feat(exhaustive): Add support for passing a fallback function#253
Merged
feat(exhaustive): Add support for passing a fallback function#253
Conversation
Closed
|
Is there anything we can do to make this solution implemented? |
12c067e to
5841013
Compare
|
Hello @gvergnaud, I have a question: What can I do to include this awesome feature in the release? It would really help me write clean and safe pattern matching even in production. |
Owner
Author
|
I think I'll include it in the next release. I'll try to ship it in the next few weeks |
8151846 to
1f8e197
Compare
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.
Solves #144 #218 and replaces #38 #219
Docs
By default,
.exhaustive()will throw an error if the input value wasn't handled by any.with(...)clause. This should only happen if your types are incorrect.It is possible to pass your own handler function as a parameter to decide what should happen if an unexpected value has been received. You can for example throw your own custom error:
Or log an error and return a default value: