[Improvment]: LC0092 - Target global and local variables separately

[pibcht]

Analyzer

LinterCop

Issue type

Other

Rule ID

LC0092

Description

I would like LC0092 to distinguish between local variables and global variables when checking naming conventions.

In our coding standard, local variables use lowerCamelCase, while global variables follow the usual PascalCase rule. Currently, LC0092 seems to apply the same name check to both, which makes it impossible to enforce this convention cleanly.

It would be useful to have separate configuration options for local and global variables, so projects using non-Microsoft naming conventions can still rely on LC0092 without disabling the rule entirely.

Thanks 🫶🏻

AL code to reproduce

Additional context

No response

[pibcht]

📌 While wandering through the discussions I came across this commit which seems to add the requested additional types : MODUSCarstenScholling@9c65b2e by https://github.com/MODUSCarstenScholling :)

[Arthurvdv]

@pibcht, yep! This is part of the Transforming private Cop to ALCops discussion, where @MODUSCarstenScholling is helping me with these contributions, so we'll be working on it together 🤗