2023-05-03 11:06:20 +02:00
|
|
|
== Why is this an issue?
|
|
|
|
|
2021-04-28 16:49:39 +02:00
|
|
|
Shared coding conventions allow teams to collaborate efficiently. This rule checks that all record field names match the provided regular rexpression.
|
|
|
|
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2023-05-03 11:06:20 +02:00
|
|
|
=== Noncompliant code example
|
2021-04-28 16:49:39 +02:00
|
|
|
|
|
|
|
With the default regular expression ``++[a-zA-Z](_?+[a-zA-Z0-9])*+++``:
|
|
|
|
|
2022-02-04 17:28:24 +01:00
|
|
|
[source,sql]
|
2021-04-28 16:49:39 +02:00
|
|
|
----
|
|
|
|
DECLARE
|
|
|
|
TYPE my_type IS RECORD(
|
|
|
|
foo__bar PLS_INTEGER -- Non-Compliant
|
|
|
|
);
|
|
|
|
BEGIN
|
|
|
|
NULL;
|
|
|
|
END;
|
|
|
|
/
|
|
|
|
----
|
|
|
|
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2023-05-03 11:06:20 +02:00
|
|
|
=== Compliant solution
|
2021-04-28 16:49:39 +02:00
|
|
|
|
2022-02-04 17:28:24 +01:00
|
|
|
[source,sql]
|
2021-04-28 16:49:39 +02:00
|
|
|
----
|
|
|
|
DECLARE
|
|
|
|
TYPE my_type IS RECORD(
|
|
|
|
foo_bar PLS_INTEGER -- Compliant
|
|
|
|
);
|
|
|
|
BEGIN
|
|
|
|
NULL;
|
|
|
|
END;
|
|
|
|
/
|
|
|
|
----
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2021-09-20 15:38:42 +02:00
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
|
|
|
|
'''
|
|
|
|
== Implementation Specification
|
|
|
|
(visible only on this page)
|
|
|
|
|
2023-05-25 14:18:12 +02:00
|
|
|
=== Message
|
|
|
|
|
|
|
|
Rename this record field to match the provided regular expression: xxx.
|
|
|
|
|
|
|
|
|
|
|
|
=== Parameters
|
|
|
|
|
|
|
|
.regexp
|
|
|
|
****
|
|
|
|
|
|
|
|
----
|
|
|
|
[a-zA-Z](_?+[a-zA-Z0-9])*+
|
|
|
|
----
|
|
|
|
|
|
|
|
The regular expression the field should match.
|
|
|
|
****
|
2021-09-20 15:38:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
endif::env-github,rspecator-view[]
|