docs: update README to include migration instructions for FluentAssertions and xUnit to aweXpect - #100
Merged
Merged
Conversation
…tions and xUnit to aweXpect
vbreuss
enabled auto-merge (squash)
May 3, 2026 12:45
|
|
This is addressed in release v0.6.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request updates documentation, resource strings, and comments to consistently use the correct casing for "FluentAssertions" instead of "fluentassertions" throughout the codebase. This improves clarity and professionalism in both code comments and user-facing messages.
Documentation and Resource String Updates:
Resources.resxandResources.Designer.cs.Code Documentation Improvements:
FluentAssertionsAnalyzer.cs,FluentAssertionsCodeFixProvider.cs, and test case comments to use "FluentAssertions" with correct casing.