== Why is this an issue?

Shared coding conventions allow teams to collaborate efficiently. This rule checks that all ``++Private Const++`` field names comply with the provided regular expression.


The default configuration is:

* Optionally, can start with an underscore character or "s_", e.g. ``++_foo++``, ``++s_foo++``
* Camel casing, starting with a lower case character, e.g. backColor
* Short abbreviations of 2 letters can be capitalized only when not at the beginning, e.g. "id" in productID
* Longer abbreviations need to be lower cased, e.g. html


=== Noncompliant code example

With the default regular expression ``++^(s_|_)?[a-z][a-z0-9]*([A-Z]{1,3}[a-z0-9]+)*([A-Z]{2})?$++``:

[source,vbnet]
----
Module Module1
    Private Const Foo = 0  ' Noncompliant
End Module
----


=== Compliant solution

[source,vbnet]
----
Module Module1
    Private Const foo = 0  ' Compliant
End Module
----

ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

=== Message

Rename "yyy" to match the regular expression: "xxx".


=== Parameters

.format
****

----
^(s_|_)?[a-z][a-z0-9]*([A-Z]{1,3}[a-z0-9]+)*([A-Z]{2})?$
----

Regular expression used to check the private constant names against.
****


endif::env-github,rspecator-view[]