autonomousapps / autonomousapps/dependency-analysis-gradle-plugin

Print out where in the source code specific classes are exposed in a module

Open
#934 5 comments 1 reaction 0 assignees View on GitHub
enhancement sponsorable
Dominant language
Kotlin
Stars
2.2k
Forks
158
Avg merge
16h 25m
Merged PRs (30d)
46

Description

**Is your feature request related to a problem? Please describe.**
I don't find document mentioning how I can get more detailed messages. Sometimes it shouldn't be fixed by suggesting moving from `implementation` to `api` dependency. Instead, lots of cases are we should fix the wrong accessibility modifier or do the encapsulation better by extracting interfaces or base implementations.

The problem is if it's only telling me my module is exposing something, I need to search a lot for where it's exposed, and for some legacy modules, it can be hundreds of places.

**Describe the solution you'd like**
Adding some parameters like "verbose" to print out more detailed information like where those dependency are exposed.
The path and line number of the source file would be very helpful.

Thanks in advance.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating the diagnostic that reports when a module exposes a dependency and inspect how its output is produced. Done means an opt-in verbose mode reports the source path and line number for each exposure, with coverage for the reported output.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
build-system, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.