-
Notifications
You must be signed in to change notification settings - Fork 7
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
Autoimported object has too many common names in scope #18
Comments
Wow, good point! I never thought about that at the time and in the mean time I've actually learned to use I'll try to fix this ASAP. For extra speed it would be great if you could send a PR. |
Reading up on how I did this, I now remember why it ended up like this. The obvious solutions would be:
I like the second option best. Would you agree @jvican ? |
I think the second option is better @agemooij, it addresses the issue at its root. The fewer names in |
I agree. I'll see if I can find some time to implement this. A PR would certainly help speed things up 😉 |
Would love to help, but I don't have time. |
autoImport
extends several traits that define lots of common operations likecurrentSbtVersion
,currentScalaVersion
, etcetera. https://github.com/agemooij/sbt-prompt/blob/master/src/main/scala/com/scalapenos/sbt/prompt/promptlets/promptlets.scala#L16-L36This causes name clash problems with builds that do define these names in some way or another. In my case, it failed because I had a
val currentScalaVersion = "2.12.3"
in mybuild.sbt
.This is an important problem. Sbt autoimports all those names and that's why it's good practice to reduce the names in
autoImport
as much as possible.Would it be possible that you remove all those clashing names from this excellent sbt plugin?
The text was updated successfully, but these errors were encountered: