Skip to content

Conversation

jnyrup
Copy link
Member

@jnyrup jnyrup commented May 30, 2025

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.
image
image

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 using string.Split(string separator, StringSplitOptions options = StringSplitOptions.None).

IMPORTANT

  • If the PR touches the public API, the changes have been approved in a separate issue with the "api-approved" label.
  • The code complies with the Coding Guidelines for C#.
  • The changes are covered by unit tests which follow the Arrange-Act-Assert syntax and the naming conventions such as is used in these tests.
  • If the PR adds a feature or fixes a bug, please update the release notes with a functional description that explains what the change means to consumers of this library, which are published on the website.
  • If the PR changes the public API the changes needs to be included by running AcceptApiChanges.ps1 or AcceptApiChanges.sh.
  • If the PR affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
    • Please also run ./build.sh --target spellcheck or .\build.ps1 --target spellcheck before pushing and check the good outcome

jnyrup added 2 commits May 30, 2025 17:17
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`
Comment on lines +4 to +6
#if NET6_0_OR_GREATER || NETSTANDARD2_1
using System.Diagnostics.CodeAnalysis;
#endif
Copy link
Member Author

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

#if !NETSTANDARD2_0
using FluentAssertions.Events;
#endif

Copy link
Member Author

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

Copy link

Qodana for .NET

It 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
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

@coveralls
Copy link

Pull Request Test Coverage Report for Build 15350556815

Details

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 97.322%

Totals Coverage Status
Change from base Build 15292043008: 0.0%
Covered Lines: 12459
Relevant Lines: 12657

💛 - Coveralls

@jnyrup jnyrup merged commit 45cd650 into fluentassertions:main May 30, 2025
8 checks passed
@jnyrup jnyrup deleted the qodana_problems branch June 2, 2025 19:21
This was referenced Jul 21, 2025
This was referenced Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants