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
For compatibility reasons, all table rows should have borders (pipe symbols) at the start and at the end. However, the RS2007 analyzer does not permit borders at the start or at the end of lines and raises the warning if they are provided.
Steps To Reproduce
Update the borders of a new rule or changed rule table to include a start or end border.
Example
The following is accepted (in main although not in the latest release 3.11.0)
Analyzer
Diagnostic ID: RS2007:
Invalid entry in analyzer release file
Analyzer source
NuGet Package: Microsoft.CodeAnalysis.Analyzers
Version: 3.11.0
Also tested in main
d6e7d82
Describe the bug
For compatibility reasons, all table rows should have borders (pipe symbols) at the start and at the end. However, the RS2007 analyzer does not permit borders at the start or at the end of lines and raises the warning if they are provided.
Steps To Reproduce
Update the borders of a new rule or changed rule table to include a start or end border.
Example
The following is accepted (in main although not in the latest release 3.11.0)
but the following causes an issue because of the border
Expected behavior
Allows for table tables to have included borders.
Actual behavior
Breaks best practice for compatibility by producing a warning when table borders are included.
Additional context
Previously mentioned in a comment as part of a similar issue.
The text was updated successfully, but these errors were encountered: