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
The issue you refer to was about SA1000 triggering when there were no spaces.
The behaviour you are seeing is by design. If you try Visual Studio's built in formatting (Ctrl K D), you will se that it removes the space between new and the parenthesis. At least if you are using the default formatting settings. This is the expected formatting according to SA1000: Dog dog = new(3);
This issue was previously reported and closed; however, SA1000 is still being incorrectly reported whenever the expression contains a parameter.
For example, let
Dog
be a class that defines a constructor that takes one parameter,numPaws
.Then the following invocation of the constructor will incorrectly report SA1000.
Dog dog = new (3);
The text was updated successfully, but these errors were encountered: