-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document MSTEST0037 analyzer #43601
base: main
Are you sure you want to change the base?
Document MSTEST0037 analyzer #43601
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
| **Enabled by default** | Yes | | ||
| **Default severity** | Info | | ||
| **Introduced in version** | 3.7.0 | | ||
| **There is a code fix** | No | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| **There is a code fix** | No | | |
| **Is there a code fix** | No | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"There is a code fix" could be misread by someone as that yes, there's a code fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is following the same wording as all other MSTESTxxxx docs.
https://github.com/search?q=repo%3Adotnet%2Fdocs+%22There+is+a+code+fix%22&type=code
I think it's best to address it separately for all doc pages.
Co-authored-by: Genevieve Warren <[email protected]>
Product PR: microsoft/testfx#4052 (merged already)
Internal previews