2023-05-03 11:06:20 +02:00
== Why is this an issue?
2023-08-10 16:54:47 +02:00
Functions and procedures with a long parameter list are difficult to use, as maintainers must figure out the role of each parameter and keep track of their position.
2020-06-30 10:16:44 +02:00
2023-08-10 16:54:47 +02:00
include::noncompliant.adoc[]
2020-06-30 10:16:44 +02:00
2023-08-10 16:54:47 +02:00
The solution can be to:
2020-06-30 14:49:38 +02:00
2023-08-10 16:54:47 +02:00
* Split the function or the procedure into smaller ones
2020-06-30 10:16:44 +02:00
2023-08-10 16:54:47 +02:00
include::split-example.adoc[]
2020-06-30 10:16:44 +02:00
2023-08-10 16:54:47 +02:00
* Find a better data structure for the parameters that group data in a way that makes sense for the specific application domain
2020-06-30 10:16:44 +02:00
2023-08-10 16:54:47 +02:00
include::struct-example.adoc[]
2020-06-30 14:49:38 +02:00
2023-08-10 16:54:47 +02:00
This rule raises an issue when a function or a procedure has more parameters than the provided threshold.
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
2023-05-25 14:18:12 +02:00
=== Parameters
.parameters
****
----
10
----
The maximum number of function and procedure parameters allowed.
****
2021-09-20 15:38:42 +02:00
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
2023-06-22 10:38:01 +02:00
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]