rspec/rules/S5612/java/rule.adoc

== Why is this an issue?

Lambdas (introduced with Java 8) are a very convenient and compact way to inject a behavior without having to create a dedicated class or method. But those lambdas should be used only if the behavior to be injected can be defined in a few lines of code, otherwise the source code can quickly become unreadable.


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

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

=== Message

Reduce this lambda number of lines from {} to at most {}, or make it a named class or method.


=== Parameters

.Max
****

----
20
----

Maximum allowed lines of code in a lambda
****


'''
== Comments And Links
(visible only on this page)

=== relates to: S1188

=== on 7 Nov 2019, 15:19:40 Michael Gumowski wrote:
Splitting RSPEC-1188 for java in two distinct rules:

* RSPEC-1188 targets ONLY anonymous classes
* RSPEC-5612 targets ONLY lambdas

endif::env-github,rspecator-view[]
migrate rule descriptions to new education format 2023-05-03 11:06:20 +02:00			`== Why is this an issue?`

Restructure one-lang rspecs 2021-04-28 16:49:39 +02:00			`Lambdas (introduced with Java 8) are a very convenient and compact way to inject a behavior without having to create a dedicated class or method. But those lambdas should be used only if the behavior to be injected can be defined in a few lines of code, otherwise the source code can quickly become unreadable.`
Fix the missing default metadata fields 2021-04-28 18:08:03 +02:00
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00
Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`ifdef::env-github,rspecator-view[]`
RULEAPI-666: Migrate the "List of parameters", "Highlighting" and "Message" fields from jira RSPEC (#346) 2021-09-20 15:38:42 +02:00
			`'''`
			`== Implementation Specification`
			`(visible only on this page)`

Inline adoc when include has no additional value (#1940) 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. 2023-05-25 14:18:12 +02:00			`=== Message`

			`Reduce this lambda number of lines from {} to at most {}, or make it a named class or method.`


			`=== Parameters`

			`.Max`
			`****`

			`----`
			`20`
			`----`

			`Maximum allowed lines of code in a lambda`
			`****`
RULEAPI-666: Migrate the "List of parameters", "Highlighting" and "Message" fields from jira RSPEC (#346) 2021-09-20 15:38:42 +02:00

RULEAPI-576: add a horizontal rule between rule description and comments 2021-06-08 15:52:13 +02:00			`'''`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00			`== Comments And Links`
			`(visible only on this page)`

Inline adoc when include has no additional value (#1940) 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. 2023-05-25 14:18:12 +02:00			`=== relates to: S1188`

			`=== on 7 Nov 2019, 15:19:40 Michael Gumowski wrote:`
			`Splitting RSPEC-1188 for java in two distinct rules:`

			`* RSPEC-1188 targets ONLY anonymous classes`
			`* RSPEC-5612 targets ONLY lambdas`

Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`endif::env-github,rspecator-view[]`