Expand on how sbt shell parses input

[dwijnand]

After some trial and error I understood a part of how the sbt shell parses scoped keys, which I didn't understand from the docs and, therefore, I think should be expanded upon.

Given (this was using sbt 0.13.7)

lazy val root = project aggregate core
lazy val core = project

here I'm getting the wrong answer because I'm asking the question wrong:

> test::publishArtifact
[info] core/*:test::publishArtifact
[info]     true
[info] root/*:test::publishArtifact
[info]     true

when I should be asking

> test:publishArtifact
[info] core/test:publishArtifact
[info]     false
[info] root/test:publishArtifact
[info]     false

Note, I was only able to understand because I was using a multi-module setup, which showed core/*:test::publishArtifact, which isn't what I was after. In a single module setup this would have just shown true.

[jsuereth]

This highlights @eed3si9n 's goal of unifying the Shell parsing with Scala syntax so there's less confusion.

test as the task vs. test the configuration is a large source of confusion, to me.

[dwijnand]

Indeed. In fact if the sbt shell were a REPL it would be very, very useful.. I could stop needing to drop in and out of consoleProject to do things like resolvers.eval foreach println..

[dwijnand]

This highlights @eed3si9n 's goal of unifying the Shell parsing with Scala syntax so there's less confusion.

Problem solved! (context: https://twitter.com/eed3si9n/status/913325233599336448)