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

Filter problems in mimaFindBinaryIssues #793

Closed
wants to merge 1 commit into from

Conversation

julienrf
Copy link
Contributor

Currently, mimaFindBinaryIssues does not apply the problem filters. This means that the output of mimaFindBinaryIssues may be inconsistent with what is reported by mimaReportBinaryIssues (ie, the former may be non-empty although the latter would not report any issue). Is that intentional?

In sbt-version-policy we have to re-implement the problem filtering because of that behavior.

Note that applying the filters in mimaFindBinaryIssues would require more changes than this commit: the code that implements the reporting part would have to be updated accordingly (currently, it takes the filters as parameters, and it prints the number of problems that have been filters out).

Another way to reduce the code duplication between sbt-version-policy and mima would be to make the method ProblemReporting.isReported public.

How would you like to proceed? Apply the filtering in mimaFindBinaryIssues, make ProblemReporting.isReported public, or do nothing?

Copy link
Collaborator

@dwijnand dwijnand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the right choice is changing the behaviour of mimaFindBinaryIssues. ProblemReporting.isReported seems simple enough to make public, so let's go with that.

@julienrf
Copy link
Contributor Author

Thank you for the review. I am not working on this problem anymore, but if someone is interested in taking it over from here, please feel free to do so!

@julienrf julienrf closed this Mar 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants