Skip to content
This repository has been archived by the owner on Jan 17, 2024. It is now read-only.

Addition of <publisher>.<extension-id> to configuration ID sample #106

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

GregTrevellick
Copy link

According to the Hello World with Configuration sample extension widget, the array of targets for the widget needs to contain the ID for the configuration in the form .., which in the case of the sample would be fabrikam.vsts-extensions-myExtensions.HelloWorldWidget.Configuration

However the sample source code here appears not to following this ID naming convention.

The vss-extension.json file currently contains

"targets": [ "ms.vss-dashboards-web.widget-catalog", ".HelloWorldWidget.Configuration" ],

but I suspect it should contain the following

"targets": [ "ms.vss-dashboards-web.widget-catalog", "fabrikam.vsts-extensions-myExtensions.HelloWorldWidget.Configuration" ],

…ration contribution's "targets" array

According to the [Hello World with Configuration](https://docs.microsoft.com/en-us/azure/devops/extend/develop/add-dashboard-widget?view=vsts#step-5-extension-manifest-updates-1) sample extension widget, the array of targets for the widget needs to contain the ID for the configuration in the form <publisher>.<extension-id>.<configuration-id>, which in the case of the sample would be `fabrikam.vsts-extensions-myExtensions.HelloWorldWidget.Configuration`

However the sample source code [here](https://github.com/Microsoft/vsts-extension-samples/blob/master/widgets/vss-extension.json) appears not to following this ID naming convention.

The vss-extension.json file currently contains 

`
            "targets": [
                "ms.vss-dashboards-web.widget-catalog",
                ".HelloWorldWidget.Configuration"
            ],
`

but I suspect it should contain the following

`
            "targets": [
                "ms.vss-dashboards-web.widget-catalog",
                "fabrikam.vsts-extensions-myExtensions.HelloWorldWidget.Configuration"
            ],
`
@pabrams
Copy link

pabrams commented Jan 31, 2019

Well, it doesn't exactly say you need to always do that, what it says is if you want it to support Configuration, then you have to do that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants