[Bug] Issues Not Reported using Local Connector

[joshvickerson]

🐞 Bug report

Description

I'm attempting to setup Webhint with a .hintrc file that can be committed to a project so the configuration can be shared by everyone on my team. I'm trying to run Webhint on local files only using the local connector, and it's not reporting issues I would expect it to based on examples I see in the documentation.

I have attempted this using both the CLI, and the VSCode extension but neither report issues as I think they should. The CLI tool reports no issues at all, while the VSCode Extension does report some problems, but doesn't catch the example I describe below.

At this point I'm unsure if this is a bug, or a misunderstanding on my part but as far as I can tell I've followed the setup as the documentation describes and it doesn't appear to be working.

Details

Contents of my .hintrc file:

{
    "extends": [
        "accessibility"
    ],
    "connector": {
        "name": "local"
    },
    "formatters": [
        "stylish"
    ]
}

I've setup the CLI script in my package.json like this:

"scripts": {
        ... 
        "webhint": "hint ./resources"
    },

This is a Laravel project, so all relevant files live in the resources directory. My assumption here, because the documentation is not clear, is that for the Local connector, I should provide webhint a directory to check. If I omit a directory, the output is the help (as expected). As I've configured it, the output is simply:

> hint ./resources

✔ Finishing...

If I use the VSCode extension, only 1 issue is reported in a single HTML file (not the one I have open in the editor), and it's a compat issue (dialog unsupported), not an accessibility issue. This leads me to believe there's a bug here, as the extension should be respecting the .hintrc file, if my understanding of the documentation is correct.

As a basic test, I added an input element with no associated label to an existing form that lives inside an HTML file. I would expect the CLI or extension to acknowledge the problem, but neither report it. I'm completely stuck as to what I've done wrong.

Additional Details

OS: macOS 11.2.3 Node version: 10.23.0 npm version: 6.14.8 hint version: 6.1.3 VSCode extension version: 1.5.11 VSCode version: 1.55.0

[molant]

Thanks for the report @joshvickerson

Do you have a repo we can clone to investigate? That will help us a lot.

[joshvickerson]

I'm setting this up at work so unfortunately no, I can't provide a repo for you to clone at the moment.