-
Notifications
You must be signed in to change notification settings - Fork 185
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
revert unnecessary breaking change in testkit #1275
Conversation
*except in test where we compile small virtual files
b3688a8
to
0bb614f
Compare
My change was not that clean. I can fix tests here if you want. |
0bb614f
to
29b2dc7
Compare
fullClasspath.in(testsInput, Compile).value.map(_.data) :+ | ||
semanticdbTargetRoot.in(testsInput, Compile).value |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
similar strategy as in scalacenter/sbt-scalafix@cd9efb1
@@ -170,7 +170,7 @@ class CliSemanticSuite extends BaseCliSuite { | |||
checkSemantic( | |||
name = "-P:semanticdb:targetroot", | |||
args = { | |||
val (targetroot :: classDir :: Nil, jars) = | |||
val (_ :: targetroot :: Nil, jars) = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not new to this PR, but the fact that order matters here shows that the test a bit fragile - I think it's acceptable as we don't put any ordering constraint for (external) testkit client, this is just a shortcut for fixturing, not a breaking change.
No description provided.