Fix discovery of targets whose names get mangled due to their pseudo-private nature #2883
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2844
Adds an integration test to cover this edge case, a few other permutations of it that I could come up with, and other
private
-related behavior. I'm not sure if I managed to catch all different ways these methods can be mangled, but if I missed any we can discover/add them later. This new test fails if I remove any part of the code change inGroupEvaluator.scala
I'm actually not sure if this should be an integration test or a unit test.
def
s are wrapped in nestedobject
s/trait
s/class
es, which is something that unit tests do not do realistically.private
target from the command, since it will simply not compile (beingprivate
and all), and AFAICT this is somewhere we're missing coverage (unrelated to this specific failure mode)So I went with integration test.
Pull request: #2883