-
Notifications
You must be signed in to change notification settings - Fork 35
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
Support for linting on change. #83
Comments
@alkatar21 Changing this to a feature request. What we need here is to support linting on change. Currently, we support linting on vscode-pylint/bundled/linter/linter_server.py Lines 211 to 228 in 68fe00b
A caveat with supporting on change is we may also have to support cancel request. Users may also want the ability to turnoff linting on change. /cc @luabud |
Related to microsoft/vscode-python#408 |
If we do this, it should be put behind Registration in LSP itself can be done in if setting["lintOnChange"]:
@LSP_SERVER.feature(lsp.TEXT_DOCUMENT_DID_CHANGE)
def did_change(_server: server.LanguageServer, params: types.DidSaveTextDocumentParams):
"""LSP handler for textDocument/didChange request."""
_lint_and_publish_diagnostics(params) |
Closed via #368 |
The inline hints that highlight problems in the code do not behave as expected on unsaved files. While pylance/pyright move the hints, the pylint problem hints do not.
I'm not quite sure if it's more of a bug or a feature request?
Since I do not know how best to create a gif here at least 2 images (The red lines are pylance and the blue and yellow one are from pylint.):
The text was updated successfully, but these errors were encountered: