Add offset to BugInfo.

[denuno]

It turns out it's really useful to have the offset (position in the document if it were a stream of chars) of a bug. Required, in fact, for some applications to figure out where in a document something is.

We can figure this out via line/col by having things keep tables of line/offset positions, but generally they'd need the source input to build this table, and thus another hit on the file system and whatnot (which is rough with lots of files).

The parser already has this info, so we should expose it and save any tools that use offsets versus line+column the trouble of converting the location info. This also adds a length attribute, which is a little hokey but seems to work fine (used to visually highlight the code causing the issue).

[denuno]

As the unit tests passed, I'm going to go ahead and merge this. Couple things to note:

• uses cfml.parsing 2.5.6-SNAPSHOT (first to expose offsets)
• added clearBugList to BugList, and changed the config call around a bit so the same linter can be used repeatedly
• tweaks missing semi handling a little, we might want to change this back (now it uses the token before the token it was showing, theoretically the one actually causing the issue, but while visually nicer, technically, maybe not as nice?).

[ryaneberly]

Thanks Denny

…

On Wed, Sep 13, 2017 at 2:04 AM, Denny Valliant ***@***.***> wrote: Merged #466 <#466>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#466 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFtZu5wT0hLVyNhUC9hFySSgAndBhV1pks5sh3BtgaJpZM4PVnNw> .