What problem does it solve?
Detects when a library class is missing methods the project needs but is read-only, preventing direct extension and forcing duplicated helper code across clients. It keeps teams from hacking around limitations by copying behavior into every caller and highlights when a strategic extension is warranted.
Core Features & Use Cases
- Missing Method Detection: Spot repetitive client utilities that reveal the library needs additional helpers yet cannot be changed.
- Foreign Method Guidance: Show how to add small helpers within client classes that accept the vendor object for lightweight fixes.
- Local Extension Guidance: Recommend wrapping or subclassing the third-party class for more extensive functionality so the codebase talks to a richer API.
- Use Case: When an external date class only exposes getters, decide between a foreign DateUtil helper and an ExtendedDate subclass so team code can call
addDays, format, or isWeekend.
Quick Start
Determine whether to implement a foreign method or a local extension for the read-only library class lacking new behaviors.