Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enforce good naming behavior in fields and properties
See original GitHub issueMake sure that fields, properties and events are properly named.
First, make sure that they’re not defined with a single character but also, that they respect the camelCase such as fields are to respect lowerCamelCase and properties are to respect UpperCamelCase.
Warning level : Info
Diagnostics : CC0016
As for test cases, this is straightfoward. The analyzer will verify FieldDeclarationSyntax, EventDeclarationSyntax, PropertyDeclarationSyntax and evaluate their ISymbol to find out their name. Then, a simple Regex for each of those syntax will either validate or invalidate the name that was retrieved within the ISymbol.
Basically, there would be six test case: one good and one bad foreach of the SyntaxNode that the analyzer has to evaluate. @giggio
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
And about sugest lowdash/underscore (‘_’) prefix for private fields?
@thiagolunardi I agree with you.