Update mstest0018.md #50138
Open
Update mstest0018.md #50138
+2
−4
Conversation
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
dotnet-policy-service
bot
added
dotnet-fundamentals/svc
community-contribution
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 PR updates the MSTEST0018 analyzer documentation to remove the outdated requirement that members referenced in [DynamicData] must be public.
Changes made
Removed “should be public” from both the data source and display name member rule lists.
Aligned the rule description with the current MSTest v3 behavior.
Reason for change
MSTest v3 no longer requires [DynamicData] members to be public.
The documentation previously reflected the older MSTest v2 behavior, which is now obsolete.
Related issue
Fixes #49663
Internal previews