Usage of _ in methods arguments raises SA1313
See original GitHub issueTop Results From Across the Web
StyleCopAnalyzers/documentation/SA1313.md at master
This rule is new for StyleCop Analyzers, and was not present in StyleCop Classic. Cause. The name of a parameter in C# does...
Read more >https://raw.githubusercontent.com/dotnet/runtime/8...
Interface methods should be callable by child types --> <Rule Id="CA1034" ... Use Integral Or String Argument For Indexers --> <Rule Id="CA1044" ...
Read more >stylecop - StyleCopAnalyzers/SA1313 in a positional record
So, the elements FirstName and LastName act both as a property and an argument for the constructor. As properties, these elements should be ......
Read more >CA2208: Instantiate argument exceptions correctly
When a method has a parameter, and it throws an exception type that is, or derives from, ArgumentException, it is expected to call...
Read more >Identification of Novel Thermosensors in Gram-Positive ...
Through in vivo experiments, we demonstrate that SA1313 from Staphylococcus aureus and BA5598 from Bacillus anthracis, which likely control ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing this one as won’t fix. The recommended solution for method signatures when a parameter is intentionally not used is:
For example:
Currently
IDE0060
suggests that we do in fact rename unused parameters to_
:However, if we follow that advice, given by the IDE, then we run into this issue. That doesn’t seem like a good thing to Won’t Fix