|
|
RSPEC-5001
|
RSPEC-134
Apex
|
Unassigned
|
Quentin Jaquier
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4931
|
RSPEC-134
Scala: Control flow statements "if", "for", "while", "match" and "try" should not be nested too deeply
|
Unassigned
|
Pierre-Yves Nicolas
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4762
|
RSPEC-134
Ruby: Control flow statements "if", "for", "while", "until", "case" and "begin...rescue" should not be nested too deeply
|
Unassigned
|
Christophe Zurn
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4701
|
RSPEC-134
Kotlin: Control flow statements "if", "for", "while", "when" and "try" should not be nested too deeply
|
Unassigned
|
Marcelo Sousa (Inactive)
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4594
|
RSPEC-134
Go: Control flow statements "if", "for" and "switch" should not be nested too deeply
|
Unassigned
|
Alexandre Gigleux
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4497
|
RSPEC-134
T-SQL: Control flow statements "IF", "WHILE" and "TRY" should not be nested too deeply
|
Unassigned
|
Christophe Zurn
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4215
|
RSPEC-134
PL/I: "if" statements should not be nested too deeply
|
Unassigned
|
Pierre-Yves Nicolas
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-3534
|
RSPEC-134
C#: Control flow statements "if", "switch", "for", "foreach", "while", "do" and "try" should not be nested too deeply
|
Unassigned
|
Tamas Vajk (Inactive)
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-3102
|
RSPEC-134
VB.NET: Control flow statements "If", "For", "For Each", "Do", "While", "Select" and "Try" should not be nested too deeply
|
Unassigned
|
Massimo Paladin
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2843
|
RSPEC-134
C-Family
|
Unassigned
|
Evgeny Mandrikov
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2725
|
RSPEC-134
Cobol: Control flow statements should not be nested too deeply
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2724
|
RSPEC-134
RPG: Control flow statements "IF", "FOR", "DO", ... should not be nested too deeply
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2723
|
RSPEC-134
ABAP: Control flow statements "IF", "CASE", "DO", "LOOP", "SELECT", "WHILE" and "PROVIDE" should not be nested too deeply
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2722
|
RSPEC-134
PHP
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2721
|
RSPEC-134
JavaScript
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2720
|
RSPEC-134
Flex: Control flow statements "if", "for", "while" and "switch" should not be nested too deeply
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2719
|
RSPEC-134
Java
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2679
|
RSPEC-134
Python: Control flow statements "if", "for", "while", "try" and "with" should not be nested too deeply
|
Unassigned
|
Elena Vilchik
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2489
|
RSPEC-134
Swift: Control flow statements "if", "for", "for in", "while", "do while" and "switch" should not be nested too deeply
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2399
|
RSPEC-134
PL/SQL: "IF" statements should not be nested too deeply
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|