Introduces an attribute to mark an entire assembly as one that contains custom assertions.#2389
Merged
dennisdoomen merged 1 commit intofluentassertions:developfrom Oct 18, 2023
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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