Introduces an attribute to mark an entire assembly as one that contains custom assertions.

[dennisdoomen]

Instead of marking individual methods with the [CustomAssertion], you can now add the [assembly: CustomAssertionsAssembly] attribute to a file within the project to tell Fluent Assertions that all code in that assembly should be treated as custom assertion code.

Part of the solution to resolve #2002

[github-actions]

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/[email protected]
        with:
          upload-result: true

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[coveralls]

Pull Request Test Coverage Report for Build 6526061737

• 5 of 6 (83.33%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.01%) to 97.397%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
Src/FluentAssertions/CallerIdentifier.cs	5	6	83.33%

Totals
Change from base Build 6525413142:	-0.01%
Covered Lines:	11655
Relevant Lines:	11846

---

💛 - Coveralls