-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
linter-xo
does not report problems
#73
Comments
I had the same problem, I just found out that you must set the {
"xo.enable": true
} ...regardless of what's in your package.json. |
@papb I had it set globally in vscode... with no luck... yet. |
@PopGoesTheWza Really? Weird... Good luck... Perhaps try reinstalling extensions, or even reinstalling VSCode itself, I don't know... |
With no clear explanation, it finally started to report problems into the vscode Problems window. It suddenly "kicked-in" during an hours long vscode session. I had
My {
"ignores": [".js"],
"space": 2,
"prettier": true
} Now there's still something bothering me, though it may be WAD, but problems reported do not offer option for quick-fix nor to open the rule documentation like |
@PopGoesTheWza still have an issue? |
I have the latest
xo
cli installed and working from the terminal.package.json
hasxo
settings:But inside vscode, does not report anything to the 'problems' viewport, and invoking 'Fix all auto-fixable problems' from the command palette does not fix anything.
The text was updated successfully, but these errors were encountered: