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

Is modifying current workspace available? #4938

Open
QingCold opened this issue Mar 12, 2024 · 4 comments
Open

Is modifying current workspace available? #4938

QingCold opened this issue Mar 12, 2024 · 4 comments
Assignees

Comments

@QingCold
Copy link

QingCold commented Mar 12, 2024

Is your feature request related to a problem? Please describe.
I recently open a complex project containing multi submodules which each owns a '.git'.
So I wonder if there is a method that let me modify current workspace so that my lsp can run correctly.

Describe the solution you'd like
I'd like to use CocCommand to modify the workspace.
e.g. workspace.setCurrentWorkspace("/path/to/myproject/")

@QingCold
Copy link
Author

My current solution is : bind call CocAction('AddWorkspaceFolder','path') to a command. Then execute CocCommand -- intelephense.index.workspace

@fannheyward
Copy link
Member

fannheyward commented Mar 12, 2024

There's currently no way to set workspace root.

coc.nvim resolved root for current document with root patterns, for monorepo with multi root patterns, the resolving maybe correct for some but fail for others.

Similar issues:

Will improve the resolving for monorepo.

@QingCold
Copy link
Author

There's currently no way to set workspace root.

coc.nvim resolved root for current document with root patterns, for monorepo with multi root patterns, the resolving maybe correct for some but fail for others.

Similar issues:

Will improve the resolving for monorepo.

So is there a need to add feature 'set workspace root' ? I thought it will be better. Hope this does not bother you. :)

@ZSaberLv0
Copy link
Contributor

vim-lsp support root_uri option (as callback function) to register LSP, maybe it's a better way

@fannheyward fannheyward self-assigned this Oct 11, 2024
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

3 participants