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.
Right now the cli works fine with plugins and extensions. When adding for example the vue plugin I've updated my package.json with this and xo finds the issues. Yet when I open Atom I get no linter issues showing up at all.
Correct. I think we need a mapping between known file extensions and Atom scopes, and then check whether the user added any of the supported scopes from the "extensions" option and then add it to SUPPORTED_SCOPES. Could also take a look at how for example atom-linter-eslint solves this.
@marionebl Correct, the list of scopes that linter-eslint tells linter it should run on is determined entirely from the user config since we have no way of knowing all the possibilities that are out there with ESLint processors.
The known supported scripts are set as the default in the settings, users can add more if they want.
You can also find an alternative approach in use for the lintHtmlFiles setting: If that setting is enabled we add the embedded HTML scope to the current list (whatever it may be), and remove it on disabling of the setting. (here)
Right now the cli works fine with plugins and extensions. When adding for example the
vue
plugin I've updated mypackage.json
with this andxo
finds the issues. Yet when I open Atom I get no linter issues showing up at all.I'm guessing this is what's causing the issue.
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: