Extensions publish do not warn/error on invalid extensionDependencies

[Tyriar]

• VSCode Version: Code - Insiders 1.6.0-insider (c94c824, 2016-09-28T06:23:37.103Z)
• OS Version: Linux x64 4.4.0-38-generic, Ubuntu 16.04
  Test: Install a set of extensions #12647

I published an extension without errors with the following extensionDependencies:

    "extensionDependencies": [
        "[email protected]",
        "Tyriar.lorem-ipsum"
    ]

It published fine but when installed it only installs Tyriar.lorem-ipsum.

[sandy081]

Added a warning for invalid identifiers, but not for non-existing ones.

[mjbvz]

@sandy081 I see the entry now marked in vscode

Two questions about the expected behavior though:

• Should "[email protected]" generate warnings or errors when you run vsce publish on the command line?
• Should entries for non-existant packages such as "nonsuch.package" generate errors?

[sandy081]

@mjbvz

Should "[email protected]" generate warnings or errors when you run vsce publish on the command line?

Yes, it does not allow

Should entries for non-existant packages such as "nonsuch.package" generate errors?

VSCE will publish them as new extensions if does not exist. I am not showing any squiggles for non-existent packages. It is just for invalid identifiers.

[mjbvz]

Ok, I'm still allowed to vsce publish an extension with errors for "[email protected]" using vsce 1.35.0

Reopening

[sandy081]

@mjbvz I see what you mean. Currently VSCE only validates extension names not extension dependencies. I meant this in my above comment. Sorry, I was not clear.

Fix here is to show only squiggles for invalid extension dependencies.

Created an issue in VSCE to validate extension dependencies while publishing - microsoft/vscode-vsce#227

Since you confirmed the squiggles, I am closing this as verified.