Closed RoieSantos closed 4 years ago
Well, even Microsoft is not yet compliant with their own rules :) If this warning annoys you, you can disable it in a ruleset file until Microsoft fix the control name.
It should be ok to refer to to something with a quote in. Warning should only appear on the actual definition.
fixed in master
Describe the bug We are currently updating our extension to BC16 in the ${CodeCop} declared under code analyzer it is showing multiple warnings. Below is one "AL0100 Do not have identifiers with quotes in the name"
To Reproduce Steps to reproduce the behavior:
Screenshots![image](https://user-images.githubusercontent.com/63336107/78773734-04949f80-79d7-11ea-8913-0c29712a5462.png)
Standard Code BC16![image](https://user-images.githubusercontent.com/63336107/78773874-360d6b00-79d7-11ea-856c-efe373b8f307.png)
Versions: AL Language 5.0.254558 Business Central : 16.0.11209.0 (Preview)