HIGHLIGHT Product Documentation

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

• Importing naming collisions can cause risks
• Long try blocks can cause risk in code
• Global Variables can easily change module behavior
• Empty and Implicit Returns cause resiliency issues.
• Conflicts in Local / Global Variables can be Unproductive
• Unused arguments are quite risky for the code.
• Always call ancestor to avoid risks in Python code
• Multiple Significant Returns are risky for the code
• Unused imports cause risks in code
• Unused variables can cause risks in code
• Automatic numbering increases costs
• Backslash line continuation makes code less readable
• len() as upper boundary makes code less readable
• Multiline Conditional Expressions should be avoided
• Improper Indentation can reduce readability
• How to scan a Git repo with the Command Line (using Apache Ant)
• Avoid Main Procedures not having an ON ERROR clause
• Avoid unused Function parameters
• Missing default in switch statements can cause Production Risk
• Avoid using SELECT ... ENDSELECT statement
• Avoid using "SELECT DISTINCT", use DELETE-ADJACENT
• Avoid Main Procedures having complex queries
• Avoid using dynamic queries
• Avoid classes overriding only equals() or only hashCode()
• How to integrate Highlight's Command Line in a Jenkins Pipeline
• Type() can hamper productivity
• Truncate tables compromise backups
• The code contains too many includes.
• Nested Loops cause performance issues
• Explicit Option makes declaring variables easier