HIGHLIGHT Product Documentation

This documentation is for reference only. Original Highlight Product Documentation is available at https://doc.casthighlight.com/

• Avoid long 'if/else if' chains that could be replaced by a 'switch' statement
• phpinfo() should not be used in production
• Avoid useless overriding method
• The code contains too many uppercase control structure keywords
• The code contains too many PHP4 deprecated constructor naming.
• The code contains too many functions, interfaces or classes with closing not commented
• The code contains too many functions throwing exceptions that have inconsistencies in "@throws" tags
• The code contains too many functions not complying with naming conventions
• The code contains too many final artifacts in final classes
• The code contains too many classes that declare __get() without declaring __set()
• The code contains too many class names that do not begin with an uppercase letter
• Force casts should not be used
• Prefer to use an expression body for functions whose body consists of a single expression
• Avoid abstract classes without abstract or concrete methods
• Use short variable declarations (:=) for variables with default values
• Avoid naming unused receivers
• Avoid instantiation with new
• Avoid 'switch' with too many 'case' statements
• Variables should not be shadowed
• Variables should be declared with 'let' or 'const'
• Multiline string literals should not be used
• Logical OR should not be used in switch cases
• In switch 'default' clauses should be last
• Avoid caching selector for long time
• URIs (URL & path) should not be hardcoded for testability purpose
• try! should not be used
• A field should not duplicate the name of its containing class
• Use == instead of ?: when dealing with nullable boolean
• The code contain too many unused private methods
• Prefer using expression Form for ‘if’ or ‘when’ in place of statement syntax