Allow diagnostics to only report on save, or with delay, instead of as-you-type

[BelugaHaechi]

A major feature of Pylance is "as-you-type reporting of code errors and warnings (diagnostics)", according to the extension description.

However, some may find it unnecessary to have diagnostics updated every single time when a new char is typed. In the process of writing new code, nearly every intermediate step is an "error" if evaluated on its own. Therefore, as-you-type diagnostics will raise errors most of the time, even if the user will obviously fix the error within seconds.

Modern spell-checking tools know to wait a while for the user to stop typing before checking for errors and displaying the squiggle lines. It would be great if Pylance also has this feature, where diagnostics stops updating when the user has been recently typing.

Furthermore, it would be beneficial to just have the diagnostics every once in a while, such as on save, when the user mentally stops to check for problems in the code.

The requested feature is an option configurable in settings, to report diagnostics either only on save, or with xxx ms delay after the last input. The current default is a ~0 ms delay.

[github-actions[bot]]

Hi @BelugaHaechi, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

---

Duplicate Issues – These issues appear to be duplicates of your report.

• diagnostic error hints when typing are sometimes annoying #6668
• Option to only show errors/warnings on save #4269

---

The team will respond to your issue shortly. Please note this is a trial feature and may not be fully accurate. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or was incorrect, please give it a 👎. Your feedback helps us improve!

[BelugaHaechi]

These duplicate issues do partially describe this issue, but the most recent update was 8 months ago, which may not reflect the current state of things.

It is especially notable that the feature described may have likely been supported in previous versions, suggestive of a bug introduced in more recent versions that broke the feature.

[rchiodo]

Transferring to discussion item for up votes.

[rchiodo]

We don't actually decide when analysis runs anymore. VS code does. VS code asks us for the errors for a file. I actually think this would make more sense as a VS code enhancement request.

[BelugaHaechi]

Thank you for your reply! Indeed, this has been noted in a previous issue, but perhaps that author did not put the issue forward to VS Code. Do you think I should open a separate issue under VS Code?

It has been a few years, and it seems that linting frequency is also no longer controlled by pylint, for comparison.

[rchiodo]

I think it would be a good idea to open an issue on VS code.

[BelugaHaechi]

Thanks, I will do so shortly; hopefully work can be done to get the feature back.

[BelugaHaechi]

I would also like to ask how upvotes work, is there a certain threshold number of upvotes required for an issue to be considered addressing in development?

[rchiodo]

There's not a set number but rather just sort order of requests by number of up votes.