chore(deps): update dependency fluentassertions to 6.12.2 #206
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:
6.12.0
->6.12.2
Release Notes
fluentassertions/fluentassertions (FluentAssertions)
v6.12.2
Compare Source
What's Changed
Others
Full Changelog: fluentassertions/fluentassertions@6.12.1...6.12.2
v6.12.1
Compare Source
What's Changed
Improvements
BeEmpty()
andBeNullOrEmpty()
performance forIEnumerable<T>
, by materializing only the first item - #2530Fixes
DateTimeOffset
withBeWithin(...).Before(...)
- #2312BeEquivalentTo
will now find and can map subject properties that are implemented through an explicitly-implemented interface - #2152because
andbecauseArgs
were not passed down the equivalency tree - #2318BeEquivalentTo
can again compare a non-genericIDictionary
with a generic one - #2358FormattingOptions
were not respected in innerAssertionScope
- #2329true
andfalse
in failure messages and make them formattable to a customBooleanFormatter
- #2390, #2393NotBeOfType
when wrapped in anAssertionScope
and the subject is null - #2399BeWritable
/BeReadable
when wrapped in anAssertionScope
and the subject is read-only/write-only - #2399ThrowExactly[Async]
when wrapped in anAssertionScope
and no exception is thrown - #2398[Not]HaveExplicitProperty
when wrapped in anAssertionScope
and not implementing the interface - #2403[Not]HaveExplicitMethod
when wrapped in anAssertionScope
and not implementing the interface - #2403BeEquivalentTo
to excludeprivate protected
members from the comparison - #2417BeEquivalentTo
on an emptyArraySegment
- #2445, #2511BeEquivalentTo
with a custom comparer can now handle null values - #2489AssertionScope(context)
create a chained context - #2607AssertionScope
constructor would not create an actual scope associated with the thread - #2607ThrowWithinAsync
not respectingOperationCanceledException
- #2614BeEquivalentTo
with anIEqualityComparer
targeting nullable types - #2648Full Changelog: fluentassertions/fluentassertions@6.12.0...6.12.1
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.