webhintio / webhint-ado-extension Goto Github PK

We need to publish the extension in the market place. Probably start with 0.0.1 and not make any noise about it 🙃

I've managed to publish the extension to the webhint org and I'm running some tests. Unfortunatelly it doesn't detect the hint installation:

I believe this is because which might not detect correctly devDependencies.

We recommend hint to be installed as a devDependency so we need to find a way to fix this.

This is related to #9

It could benefit from the release script, linters, etc.

@webhintio/core thoughts?

Based on this StackOverflow answer it looks like we have to publish every time we want to test a change and that if we want to avoid releasing to everybody that already uses it we should use different names, etc.

We should have a script that bumps the version and changes the required IDs to whatever needs to be depending on where we are publishing.

@mamichae @danlope @vinodkumarys do you know if there's an easier way to test this or a script that already does this (or something similar)?

Looks like the UI of Azure DevOps has migrated to react and the advice is to use azure-devops-extension-sdk.

Plan is to still use the generated HTML instead of using their components but we need to see how everything works with this SDK.

There are examples in https://github.com/Microsoft/azure-devops-extension-sample

Right now the extension continues even if errors were found.

We should add an option so the user can decide what to do that should be "fail" by default.

Right now the project structure looks like this:

We can probably move the contents of WebhintV1 into the root.

@mamichae @danlope @vinodkumarys is there any known limitation for this?

The current code creates a .hintrc file if none is found that extends from web-recommended.
The default one already does this so we can probably avoid this step. The user will get the output that a default configuration hasn't been found but I think we want them to "investigate" a bit how to tweak it to what they need.

Epic to track the work necessary to publish v1 of the ADO extension

Right now the extension seems to be looking for the global installation.
We should check if the project already has one installed as a devDependency and if so, use it.

We could look into the package.json of the project, or inside node_modules/bin or something similar