Converted AsyncFunctionAssertions into real base class#2359
Converted AsyncFunctionAssertions into real base class#2359dennisdoomen merged 5 commits intofluentassertions:developfrom
Conversation
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 View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2023.2.6
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
jnyrup
left a comment
There was a problem hiding this comment.
Great to get rid of some new modifiers 🧹
Src/FluentAssertions/Specialized/NonGenericAsyncFunctionAssertions.cs
Outdated
Show resolved
Hide resolved
Src/FluentAssertions/Specialized/AsyncFunctionAssertionsBase.cs
Outdated
Show resolved
Hide resolved
|
Does anybody know why the Qodana build fails? |
|
Fix Qodana complaints? |
I would like to ask @dennisdoomen . The code follows the single return rule, Dennis requested in the past. |
I think we can safely remove that rule. It's too rigid to always apply. I'm fine if you update the |
Similar to what we did in fluentassertions#2359
As listed in #1677 and started in #1972, I converted AsyncFunctionAssertions into "real" base class (protected constructor).
Further, I moved some methods from base class into concrete class to prevent from overwriting (using
newkeyword).IMPORTANT
./build.sh --target spellcheckor.\build.ps1 --target spellcheckbefore pushing and check the good outcome