Revert: breaking changes (compared to 2.0.1) #130
Conversation
This file contains 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
.NET 6 support removal from amantinband#104 reverted while maintaining .NET 8 support
Throwing exceptions upon invalid usage of library from amantinband#105 reverted. Behavior of following actions is now being restored: 1. Default `ErrorOr` constructor invocation. 2. Accessing `ErrorOr.Errors` and `ErrorOr.FirstError` on success result. 3. Accessing `ErrorOr.Value` on result with errors.
zbyszekprasak
changed the title
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.
This pull requests contains CHANGELOG supplementation from #127 and reverts backwards incompatible changes regarding:
Reverted was only significant changes, not refactorings nor renames.
This PR is only for the purpose of fostering 2.1.0 release. @amantinband please merge if you agree about that it is more value in reverting those changes temporarily. I will reapply those changes soon after 2.1.0 release as a separate PR.
See: #115