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
{{ message }}
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
At it's absolute root, this is a combination ESLint and Atom issue.
Some ESLint rules give a full start line:col and end line:col, allowing the range highlighted to come straight from ESLint. The problem is that most ESLint rules only return a single line:column as the location for the rule, which means some guessing as to the end of the range has to be made. When this is all the information that is available the fallback to to use the regex from Atom's language-javascript that defines a "word" to determine how long to make the range. In this case it seems the definition of "word" stops on a - character.
I know there is some effort to majorly expand the number of rules that ESLint provides a range result for, I'm not sure how outdated xo is on the version of ESLint it bundles so it's possible an update of that will fix some cases. The "word" definition from Atom unfortunately most likely can't be changed since it must be very generic (It's not just words in strings).
tl;dr: The best that can be done about this is already being done, and time will fix this in more and more cases.
If there's an issue with importing a js package only the first half of the package name is highlighted when there's a dash in it.
Ref: steelbrain/linter#1440
IssueHunt Summary
Sponsors (Total: $40.00)
Become a sponsor now!
Or submit a pull request to get the deposits!
Tips
The text was updated successfully, but these errors were encountered: