coding-guidelines-java

Apply comprehensive coding guidelines to standardize Java and Spring Boot code quality by enforcing best practices like immutability, constructor injection, proper generics usage, and resource management with try-with-resources. This reduces manual review effort and prevents technical debt accumulation across your codebase.

Spring Boot best practices include using constructor injection instead of field injection, type-safe @ConfigurationProperties for configuration, and WebClient for HTTP requests. These patterns ensure robust, testable applications that follow modern Spring conventions and reduce coupling.

Refactoring for immutability involves applying Effective Java principles: using final classes and fields, composition over inheritance, proper generics with PECS (Producer Extends, Consumer Super), and avoiding raw types. Automated guidelines ensure consistent application across modules and reduce defects.

Yes, apply coding guidelines during code generation and project setup to ensure new code is production-ready and follows standards from inception. This covers immutability, dependency injection, testing patterns, and Spring-specific conventions automatically.

Parameter validation ensures input correctness early in execution, while resource management uses try-with-resources to automatically close file streams, database connections, and other resources. Together they prevent leaks, null pointer exceptions, and resource exhaustion.

Coding guidelines apply to both new code generation and refactoring of existing modules. Use it when setting up new projects or modernizing legacy code to adopt consistent standards, immutability patterns, and Spring best practices across your entire codebase.