Adding the location of the parsed file in the start-event

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:

{
  pos: 0,
  line: 1,
  col: 1,
  type: 'start',
  url: '/home/text.html'
}

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.

Start by tracing the parser path that emits the start event and how the current file input reaches it. Run the existing parser or event tests, then verify that parsing a named file exposes its source location on the event while preserving the current position fields and existing consumers.