|
|
RSPEC-4988
|
RSPEC-100
Apex
|
Unassigned
|
Quentin Jaquier
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4897
|
RSPEC-100
Scala
|
Unassigned
|
Alban Auzeill
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4746
|
RSPEC-100
Ruby
|
Unassigned
|
Elena Vilchik
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-4569
|
RSPEC-100
Go: Function and method names should comply with a naming convention
|
Unassigned
|
Alexandre Gigleux
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-3589
|
RSPEC-100
Swift: Function names should comply with a naming convention
|
Unassigned
|
Tamas Vajk (Inactive)
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-3568
|
RSPEC-100
Python
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2741
|
RSPEC-100
JavaScript: Function and method names should comply with a naming convention
|
Unassigned
|
Pierre-Yves Nicolas
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2105
|
RSPEC-100
Java
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2104
|
RSPEC-100
RPG: Subroutine names should comply with a naming convention
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2103
|
RSPEC-100
ABAP
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2102
|
RSPEC-100
PHP: Method and function names should comply with a naming convention
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2101
|
RSPEC-100
Flex: Function names should comply with a naming convention
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2100
|
RSPEC-100
C-Family: Function names should comply with a naming convention
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|
|
|
RSPEC-2099
|
RSPEC-100
C#: Methods and properties should be named in PascalCase
|
Unassigned
|
Ann Campbell
|
|
Active |
Unresolved
|
|
|
None
|
None
|