Skip to content
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

Merged
merged 5 commits into from Oct 8, 2023

Conversation

lg2de
Copy link
Contributor

@lg2de lg2de commented Oct 3, 2023

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

  • 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

@github-actions
Copy link

github-actions bot commented Oct 3, 2023

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

To be able to view the detailed Qodana report, you can either:

  1. Register at Qodana Cloud and configure the action
  2. Use GitHub Code Scanning with Qodana
  3. Host Qodana report at GitHub Pages
  4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2023.2.6
        with:
          upload-result: true
Contact Qodana team

Contact us at qodana-support@jetbrains.com

Copy link
Member

@jnyrup jnyrup left a 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 🧹

@lg2de
Copy link
Contributor Author

lg2de commented Oct 5, 2023

Does anybody know why the Qodana build fails?

docs/_pages/releases.md Outdated Show resolved Hide resolved
@ITaluone
Copy link
Contributor

ITaluone commented Oct 6, 2023

Fix Qodana complaints?

@lg2de
Copy link
Contributor Author

lg2de commented Oct 6, 2023

Fix Qodana complaints?

I would like to ask @dennisdoomen . The code follows the single return rule, Dennis requested in the past.

@dennisdoomen
Copy link
Member

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 qodana.yaml as part of this PR.

@dennisdoomen dennisdoomen merged commit 3205e04 into fluentassertions:develop Oct 8, 2023
5 checks passed
jnyrup added a commit to jnyrup/fluentassertions that referenced this pull request Oct 8, 2023
@lg2de lg2de deleted the async-base branch October 9, 2023 07:08
jnyrup added a commit that referenced this pull request Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants