-
Notifications
You must be signed in to change notification settings - Fork 178
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
How can I call lint() manually for standard linter? #1511
Comments
I think you should not worry about having to apply changes of settings live as they'll be like that in only your package and not the other bazillion linter packages out there. The new settings will be applied as soon as the user changes text (for lintsOnChange providers) or saves the file (for standard linters). But if you really want to do that, the command invocation should work flawlessly. If it's not working for you then I'll be able to investigate if you can put a piece of code out there that repros the behavior. |
Thank you for your reply. I would appreciate if you investigate the code.
package.json
|
I can confirm that calling |
Well ... when running the same lines from the developer console, the linter gets triggered.
At which other point, could I trigger a re-lint after a configuration change? |
I have a standard linter like:
My linter works only on save intentionally.
So new lint result by changed setting can be applied only when a user saves although he changed a setting.
So I want to execute lint() for all open text editors directly after setting change like:
But it does nothing. lint() is not called.
How can I call lint() manually for standard linter?
Please let me know.
The text was updated successfully, but these errors were encountered: