Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement full underline on stylelint polaris in VSCode #8190

Closed
sophschneider opened this issue Jan 27, 2023 · 5 comments
Closed

Implement full underline on stylelint polaris in VSCode #8190

sophschneider opened this issue Jan 27, 2023 · 5 comments
Assignees

Comments

@sophschneider
Copy link
Contributor

sophschneider commented Jan 27, 2023

Fixed by stylelint/vscode-stylelint#358

Right now, failures in VSCode only underline the first letter of the line. This makes it hard to notice/hover over. This is because the endline isn't provided in our custom rules, there are several solutions in this stylelint issue stylelint/stylelint#5694

Image

@sophschneider
Copy link
Contributor Author

In the stylelint issue I linked above, supposedly selector-no-vendor-prefix is fixed yet in my VSCode it still only underlines one char when I enable this rule.

@sophschneider
Copy link
Contributor Author

sophschneider commented Jan 31, 2023

So it looks like the problem is coming from the VSCode Stylelint plugin which is responsible for underlining failures. They actually have a PR up stylelint/vscode-stylelint#358 that is supposed to implement it, but it hasn't been merged yet. It isn't stale, there was activity about 2 weeks ago

@sophschneider
Copy link
Contributor Author

Once the Stylelint VSCode PR is merged, we will have to add range data (endLine, etc.) to our custom rule reports, then we should have full range underlines!

@BPScott
Copy link
Member

BPScott commented Mar 24, 2023

Once the Stylelint VSCode PR is merged, we will have to add range data (endLine, etc.) to our custom rule reports, then we should have full range underlines!

It's worth pointing out that you're free to add range data at any point. Stylelint on the command line will make use of it, and then when VSCode adds support it will be leveraged there too. You're not blocked by Stylelint VSCode here.

@github-actions
Copy link
Contributor

Hi! We noticed there hasn’t been activity on this issue in a while. After 30 days, it will close automatically.

If it’s still relevant, or you have updates, comment and let us know. And don’t worry, you can always re-open later if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants