You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Introducing HTMLHint to legacy code is quite tricky. You can either disable all failing rules or ignore the file for all HTMLHint rules.
It is impossible to implement a ratcheting system where I can prevent new commits from having faults while systematically ignoring the existing faults.
This is especially the case for custom rules, where very specific problems can be detected at a very late stage and require huge amounts of labor to fix.
Describe the solution you'd like
There must be some way to retrieve the currently parsed source code location.
With that one can add an ignored source code location list to each of the rules and ignore the specific pages.
Currently the start-event looks like this:
{pos: 0,line: 1,col: 1,type: 'start'}
Adding the source code location would allow that implementation:
I tried checking every event if they contain such information but nothing was found.
I am unaware of any Node.js specific function or object to retrieve that information,
which file HTMLHint is currently working on.
The text was updated successfully, but these errors were encountered:
coliff
added
keep-unstale
The issue will not be marked as stale by the stale-bot
and removed
bot:stale
Issue marked as stale because there was no activity
labels
Aug 14, 2023
Is your feature request related to a problem? Please describe.
Introducing HTMLHint to legacy code is quite tricky. You can either disable all failing rules or ignore the file for all HTMLHint rules.
It is impossible to implement a ratcheting system where I can prevent new commits from having faults while systematically ignoring the existing faults.
This is especially the case for custom rules, where very specific problems can be detected at a very late stage and require huge amounts of labor to fix.
Describe the solution you'd like
There must be some way to retrieve the currently parsed source code location.
With that one can add an ignored source code location list to each of the rules and ignore the specific pages.
Currently the
start
-event looks like this:Adding the source code location would allow that implementation:
Describe alternatives you've considered
I tried checking every event if they contain such information but nothing was found.
I am unaware of any Node.js specific function or object to retrieve that information,
which file HTMLHint is currently working on.
The text was updated successfully, but these errors were encountered: