Skip to content
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 workspace symbols #237

Open
jgarte opened this issue Jul 6, 2022 · 9 comments
Open

Support for workspace symbols #237

jgarte opened this issue Jul 6, 2022 · 9 comments

Comments

@jgarte
Copy link

jgarte commented Jul 6, 2022

I ask because I tried using this package and it complained that pylsp does not support this feature. It worked well with pyright though.

Does pyright support symbols and pylsp not?

@ccordoba12
Copy link
Member

Correct, Pylsp doesn't support workspace symbols, sorry.

@jgarte
Copy link
Author

jgarte commented Jul 7, 2022

Is there any plans to implement it?

@ccordoba12

What's you approach to workspace symbols? Do you prefer not to use this feature?

@ccordoba12
Copy link
Member

There are no plans right now, sorry.

Maybe Jedi offers this functionality but we haven't checked because there has been little interest for it.

@astoff
Copy link

astoff commented Aug 8, 2022

For the record, I find the workspace symbols feature quite useful. One can always grep the project for def something, but that's not as handy. It would also seem relatively straightforward to implement, which gives it a pretty good cost/benefit ratio.

@ccordoba12 ccordoba12 reopened this Aug 8, 2022
@ccordoba12 ccordoba12 changed the title Are workspace symbols supported? Support for workspace symbols Aug 8, 2022
@ccordoba12
Copy link
Member

ccordoba12 commented Aug 8, 2022

It seems this is supported by Jedi, so it's feasible here. However, we're swamped with other things, so I don't know when we'll have time to implement it.

@tristone13th
Copy link

In the README I saw you mentioned that Jedi can provide this function, so does it mean we can use it well now?

@ccordoba12
Copy link
Member

No, we need to implement that functionality in the way expected by the LSP protocol here.

@jgarte
Copy link
Author

jgarte commented Sep 29, 2022

No, we need to implement that functionality in the way expected by the LSP protocol here.

@ccordoba12 Thanks for clarifying that for us.

@eyalk11
Copy link

eyalk11 commented Jan 6, 2024

Made a pull request to resolve it. #511

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

5 participants