You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is used for every occurrence where it could be used (all places VS has a code fix), including summary and return/value sections. This really clutters the documentation.
It is used once in summary and not in return/value where it could be used also.
It is used in return/value but not in summary where it could be.
It is not used at all typically where the target is not fully qualified, so VS will not offer a CodeFix but there are also times it will and it isn't used.
Inconsistent use of the "see langword" attribute.
It is seldomly used where it could be. true/True, false/False, null/Nothing, Property, Event, I don't know the full list but the CodeFix does.
Guideline would be great; I am not suggesting anyone has to go back and fix everything especially without a CodeAnalyzer (unless it was standalone it would be horribly slow and would produce too may incorrect results) but as code is touched it would be nice to have consistent rules.
The text was updated successfully, but these errors were encountered:
Everywhere there is something that can be see cref or see langword they should be. Related, docs should try to use <inheritdoc> with modifications whenever possible instead of duplicating large swaths of text. This is facilitated by not cref'ing argument Types. For example:
Inconsistent use of the "see cref" attribute.
Inconsistent use of the "see langword" attribute.
Guideline would be great; I am not suggesting anyone has to go back and fix everything especially without a CodeAnalyzer (unless it was standalone it would be horribly slow and would produce too may incorrect results) but as code is touched it would be nice to have consistent rules.
The text was updated successfully, but these errors were encountered: