The use case for this is that in the grunt-lesslint task we are using source maps to show the original less line that causes the error and since it's reporting column 0 the relevent LESS line is not as accurate as it could be.
For reference: jgable/grunt-lesslint#6
When part.col is zero (ID is in the first selector column), then this will coerce to true on the second iteration
firstIdCol = typeof firstIdCol === "undefined" ? part.col : firstIdCol;
Good catch, will update shortly.
Using an ID in a selector should report first ID col
- Grab the col the first id was found at in a selector
- Report it later instead of selector.col
- Add unit tests for single and multiple ids
@jgable: can you fetch and rebase?