HIGHLIGHT Product Documentation

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

• Do not use a labeled return for the last statement in a lambda
• Boolean checks should not be inverted
• Avoid using multiple labeled returns in lambda expression
• Avoid generic catch
• Use Elvis operator to avoid unclear syntax pattern
• Avoid undefined type on data or routines declaration
• Avoid to update static fields from instance methods
• Avoid to update parameters inside routine's bodies
• Avoid to cover two dimensional ranges with nested for loop
• Avoid Public finalize() methods
• Avoid confusing initialization for variables declared on the same line
• Avoid unexpected closure inside parentheses call
• The code is managing too many files together
• The code contains too many unnecessary COMPUTE
• The code contains too many paragraph labels not followed by a dot
• The code contains too many not aligned END instructions
• The code contains too many long PIC declaration pattern
• The code contains too many instructions that initialize zones of data with zeros or spaces
• The code contains too many data contigus levels
• The code contains too many back performs
• The code contains too many dangerous usage patterns in file management
• The code contains paragraphs having the same name
• The code contains too many bad area A usages
• Optional property declarations should use '?' syntax
• Errors should not be created without being thrown
• Avoid explicit type when it can be inferred from literal value affected
• Avoid structures initializations with unamed fields
• Avoid self-assigned variables
• Avoid binary operators with identical members
• Avoid 'if/else if' & cases statements having the same condition