Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: measure the thickness of a dependency #54

Open
SethTisue opened this issue May 2, 2018 · 1 comment
Open

feature: measure the thickness of a dependency #54

SethTisue opened this issue May 2, 2018 · 1 comment

Comments

@SethTisue
Copy link
Contributor

SethTisue commented May 2, 2018

(this came up when I gave my Sculpt talk in Chicago. can't remember who suggested it)

it would be really nice if when you aggregate at the class level or the package level, the output had some measure of the "thickness" of a dependency. probably just a count of how many individual entries were aggregated into the single entry.

this would help identify dependencies that would be especially easy to cut.

@SethTisue
Copy link
Contributor Author

informally, I used to do this all the time using Classycle, as follows.

if there was a package-level dependency I suggested of being thin, I'd disallow it in the config, run Classycle, and then eyeball how long the output is. if the output was only a few lines, the dependency was probably easy to cut.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant