Style terms
Consistency, readability, and the rules that make teams sane
Coding style is not about aesthetics — it is about communication. Consistent formatting, naming conventions, linting rules, and documentation standards reduce cognitive load and make code reviews faster and less painful. This category covers the conventions and tooling that help teams write code that reads as if one thoughtful person wrote it all.
Missing Class Comments PHP 5.0+
A class without a PHPDoc block lacks the docblock description, @package annotation, and context needed for IDE tooling, generated documentation, and new developers.
2mo ago
style beginner
Missing Function Comments PHP 5.0+
Functions without PHPDoc lose IDE parameter hints, inline documentation, and the opportunity to explain non-obvious behaviour, preconditions, and edge cases.
2mo ago
style beginner
Magic Strings
Raw string literals used directly in code as identifiers or flags — prone to typos, hard to refactor, and lacking IDE support.
2mo ago
style beginner
Method Length Guidelines
Short methods (ideally under 10–20 lines) are easier to understand, test, and name — length is a proxy for complexity.
2mo ago
style beginner
Mixed Indentation
A file using both tabs and spaces for indentation — causes misalignment across editors and tools.
2mo ago
style beginner