These "style guidelines" are used to keep the Cardinal Components codebase clean and consistent.
Basics
- Indent uses 4 spaces
- Files end with a newline (
\n) - No trailing whitespace after a line
- Markdown text may use trailing whitespace for line breaks
Naming conventions
- Modules and packages use singular names
- Module names start with
cardinal-components
Java code style
- Standard Java conventions apply
- Redundant language modifiers are omitted