schematics-cli: inconsistency in referencing collection

[Splaktar]

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
- [x] schematics

Versions

Angular CLI: 7.0.0-rc.3
Node: 10.11.0
OS: darwin x64
Angular: undefined
... 

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.9.0-rc.3 (cli-only)
@angular-devkit/core         7.0.0-rc.3
@angular-devkit/schematics   7.0.0-rc.3
@schematics/angular          7.0.0-rc.3 (cli-only)
@schematics/update           0.9.0-rc.3 (cli-only)
rxjs                         6.3.3
typescript                   2.9.2

npm ls -g --depth=0
/Users/splaktar/.nvm/versions/node/v10.11.0/lib
├── @angular-devkit/schematics-cli@0.9.0-rc.3
├── @angular/cli@7.0.0-rc.3

Repro steps

1. Create a new schematics project using schematics schematic --name=test-schematic.
2. cd test-schematic
3. npm i
4. npm run build
5. schematics ./src: --list-schematics
6. schematics .:my-full-schematic --name=test

The log given by the failure

N/A

Desired functionality

When authoring a schematic and doing manual testing locally, you do the following:
In schematics ./src: --list-schematics, you reference the collection via ./src:. This is very confusing as I tried a lot of variations before figuring this out, i.e. the following don't work: src:, .:, src/:, src/.:.
In schematics .:my-full-schematic --name=test, you reference the collection via .:.

It would be nice if .: worked for both of these. Can --list-schematics see that the package.json is there and has a collections field just like when running a schematic?

Mention any other details that might be useful

I also saw this with @angular-devkit/schematics-cli@0.9.0-rc.2.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}