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

Configure which filter strategy should be used #112

Merged
merged 6 commits into from
Nov 25, 2017

Conversation

stefanzweifel
Copy link
Owner

@stefanzweifel stefanzweifel commented Nov 19, 2017

This PR adds a new filter config to the project. It affects the ComponentFinder and is responsible of rejecting classes which should not be used in the statistics.

This should solve #46, as you could swap the filter strategy and allow vendor classes to count to the statistics.

TODO

  • Better naming (Something bugs me about "filter")

@stefanzweifel stefanzweifel merged commit c239304 into master Nov 25, 2017
@stefanzweifel stefanzweifel deleted the feature/filter-strategy branch November 25, 2017 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant