-
Notifications
You must be signed in to change notification settings - Fork 733
Fix qodana warnings #3053
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix qodana warnings #3053
Conversation
It's a leftover from 0a649cb that added polyfill for `string.Split(string separator, StringSplitOptions options = StringSplitOptions.None)`. Before that commit we used the `string[] separator` overload which requires `StringSplitOptions`
#if NET6_0_OR_GREATER || NETSTANDARD2_1 | ||
using System.Diagnostics.CodeAnalysis; | ||
#endif |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This matches how we do conditional using in
fluentassertions/Src/FluentAssertions/AssertionExtensions.cs
Lines 22 to 24 in 68825b1
#if !NETSTANDARD2_0 | |
using FluentAssertions.Events; | |
#endif |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other places in this class we just fall through to the return new AndConstraint<TAssertions>((TAssertions)this);
right below
Qodana for .NETIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at [email protected]
|
Pull Request Test Coverage Report for Build 15350556815Details
💛 - Coveralls |
Since https://github.com/fluentassertions/fluentassertions/actions/runs/14577365118/job/40886331551 we have had a red Qodana pipeline.
The timestamps matches that Github announced a shutdown of an old(er) cache service.


That improved with #3044.
Now it's just 7 warnings, which this PR takes care of.
The removal of
StringSplitOptions.None
is a leftover from 0a649cb where I introduced and started usingstring.Split(string separator, StringSplitOptions options = StringSplitOptions.None)
.IMPORTANT
./build.sh --target spellcheck
or.\build.ps1 --target spellcheck
before pushing and check the good outcome