Skip to content

[FEATURE REQUEST] Diagnostics for full project #395

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

Closed
albilu opened this issue Jun 18, 2023 · 3 comments
Closed

[FEATURE REQUEST] Diagnostics for full project #395

albilu opened this issue Jun 18, 2023 · 3 comments

Comments

@albilu
Copy link

albilu commented Jun 18, 2023

Hi there,

Is there any chance that pylsp will at some point implement a switch for diagnostics for the full workspace, as mentioned for pyright in this comment #143 (comment) ?

E.g. for static type checkers like mypy it does make sense to see possible bad side effects of changes in type declarations in other files. And it would be useful in general too, e.g. for activating it just before pushing a large change.

Thanks for the great work!

Originally posted by @JesusTorrado in #280

It will be great to have this feature wich will benefit all clients using this LSP server.

@ccordoba12
Copy link
Member

Closing as a duplicate of discussion #280 (I don't understand why you reposted the original comment from there here).

@albilu
Copy link
Author

albilu commented Jun 18, 2023

@ccordoba12 I litteraly asked in that discussion if it was ok to open the topic as feature request!.

Are Feature request handle in discussions? What is the proper way to ask for a feature for this project??

@ccordoba12
Copy link
Member

It doesn't matter that much if that's a discussion or a feature request. What's needed is someone from the community willing to implement that functionality because we don't have time to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants