-
Notifications
You must be signed in to change notification settings - Fork 698
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
Converted AsyncFunctionAssertions into real base class #2359
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: true Contact Qodana teamContact us at qodana-support@jetbrains.com
|
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.
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
new
keyword).IMPORTANT
./build.sh --target spellcheck
or.\build.ps1 --target spellcheck
before pushing and check the good outcome