chore: refactored APIs to reduce coupling

[petruki]

This pull request refactors the path processing and printing components to improve modularity and code clarity by introducing new interfaces and a factory class. The changes replace concrete class references with interface-based abstractions, making the codebase more extensible and maintainable. Additionally, several classes were moved into a new package structure for better organization.

API Abstraction and Interface Implementation

• Introduced the DotPath and DotPrinter interfaces in src/main/java/io/github/trackerforce/path/api/, defining common APIs for path processing and JSON printing, respectively. Existing classes like PathCommon and PathPrinter now implement these interfaces. [1] [2] [3] [4] [5]

Factory Pattern and Dependency Injection

• Added the DotPathFactory class to centralize the creation of DotPath and DotPrinter instances, replacing direct instantiation with factory methods. This improves dependency management and testability. [1] [2]

Package and File Structure Organization

• Moved core path-related classes (PathCommon, PathExclude, PathFilter, PathPrinter, ExclusionNode) to the new io.github.trackerforce.path package, improving codebase structure and separation of concerns. [1] [2] [3] [4] [5] [6]

Refactoring for Interface Usage

• Updated DotPathQL to use DotPath and DotPrinter interfaces instead of concrete classes, and to obtain instances via DotPathFactory, further decoupling implementation details from usage. [1] [2]

These changes collectively enhance the flexibility and maintainability of the path processing and printing logic in the codebase.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
92.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud