fluentassertions / fluentassertions.analyzers

Analyzers based on the FluentAssertions best practices docs
https://www.fluentassertions.com/tips
MIT License
137 stars 21 forks source link

Checklist of all tips and whether they have analyzers #274

Closed Arithmomaniac closed 8 months ago

Arithmomaniac commented 10 months ago

Instead of tracking https://fluentassertions.com/tips/#improved-assertions piecemeal (e.g. #245) there should be an issue checklist in this repo with a here, with each suggested improvement listed as a task.

Arithmomaniac commented 10 months ago

If it is preferred to link to each analyzer when it exists on the "tips" page instead, I can create an issue in the main repo

Meir017 commented 10 months ago

Instead of tracking https://fluentassertions.com/tips/#improved-assertions piecemeal (e.g. #245) there should be an issue checklist in this repo with a here, with each suggested improvement listed as a task.

I was thinking of having a test project with test-cases for all of the different tips, it will serve as documentation and an integration test that runs dotnet format

Meir017 commented 8 months ago

@Arithmomaniac I was thinking of something like this - image

https://github.com/fluentassertions/fluentassertions.analyzers/pull/307/files#diff-40f9cb87232fc6df6199d10de09342f50ff38d1f153bfa1c77e8b62e878494f8

this way the asserts are evaluated in the CI to make sure the old/new asserts have the same result

Arithmomaniac commented 8 months ago

@Meir017 I love it