-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lifting for html works only with manual activation in the settings #1265
Comments
|
Can you please provide me with a GitHub repository I can clone that demos what you are experiencing. |
@dbaeumer I have create a repo here: Images with no alt description should be an error but they are not. Thanks for helping :) |
@lampewebdev just to check: does validation happen correctly in the terminal? |
And which file do I need to open to see the missing error? |
@dbaeumer
|
OK. As already noted a workaround is to add the probe list to the validate setting. This makes it work. I need to investigate why the probing alone doesn't work in this setup. |
@dbaeumer Maybe I miss understand but I have added the probe setting in the settings.json:
And this does not fix it for me |
Hi guys.
I'm transferring an Angular project from tslint to eslint. I ran into a problem that eslint didn't highlight errors in Angular component templates, more precisely eslint didn't highlight errors in .html files, but it highlighted errors in all other file types (I looked at the files .ts and .js and .json) in VSCode
I fixed this issue by adding one line to
settings.json
:"eslint.validate": ["html"],
eslint now highlights errors in .html files and in those files in which it highlighted errors before.
But why did it highlight errors in all files except .html before? And why with this setting it highlights errors not only in .html files? In my opinion, it will be clearer when the parameter " eslint.validate" is not set, then error highlighting works either in all files whose formats are supported by eslint, or error highlighting should not work anywhere at all.
That's how it was before I applied that setting to eslint:
This is how it became after I applied this setting to eslint:
This is the .eslintrc.json file that is located in the root of the project:
And this is the .eslintrc.json file, which is located in one of the project's applications and this file is closest to the. html file that I took a screenshot of.
The text was updated successfully, but these errors were encountered: