16f6c0aecf
Inline adoc files when they are included exactly once. Also fix language tags because this inlining gives us better information on what language the code is written in.
58 lines
863 B
Plaintext
58 lines
863 B
Plaintext
== Why is this an issue?
|
|
|
|
Shared coding conventions allow teams to collaborate efficiently. This rule checks that type names match the provided regular expression.
|
|
|
|
|
|
=== Noncompliant code example
|
|
|
|
With the default regular expression ``++[a-zA-Z]([a-zA-Z0-9_]*[a-zA-Z0-9])?++``:
|
|
|
|
[source,sql]
|
|
----
|
|
DECLARE
|
|
TYPE Collection_type_ IS VARRAY(42) OF PLS_INTEGER; -- Noncompliant
|
|
BEGIN
|
|
NULL;
|
|
END;
|
|
/
|
|
----
|
|
|
|
|
|
=== Compliant solution
|
|
|
|
[source,sql]
|
|
----
|
|
DECLARE
|
|
TYPE collectionType IS VARRAY(42) OF PLS_INTEGER;
|
|
BEGIN
|
|
NULL;
|
|
END;
|
|
/
|
|
----
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
=== Message
|
|
|
|
Rename this type to match the provided regex: xxx.
|
|
|
|
|
|
=== Parameters
|
|
|
|
.regexp
|
|
****
|
|
|
|
----
|
|
[a-zA-Z]([a-zA-Z0-9_]*[a-zA-Z0-9])?
|
|
----
|
|
|
|
The regular expression the name should match
|
|
****
|
|
|
|
|
|
endif::env-github,rspecator-view[]
|