Enable ".Which" extension for value-containing assertions #3
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 enables the FluentAsserts
.Which
sub-assertion helper when asserting on a value-containing state of a monad (BeSome, BeLeft, etc).One odd thing that I found when implementing this is that
LanguageExtTryAssertions.BeFail
returns anException
type when converted to anEither
in order to grab the failure message. However,LanguageExtTryAsyncAssertions.BeFail
returns anError
type. I've left this difference as is, but it may be confusing for an end user. I'm not exactly sure why LanguageExt is returning a different type in this case. We can either leave it, make both useException
, or make both useError
. Not sure what the best choice is, so it is up to you.Resolves #2