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

Implement workspace file/folder LSP handlers #26

Closed
4 of 8 tasks
retailcoder opened this issue Feb 24, 2023 · 0 comments
Closed
4 of 8 tasks

Implement workspace file/folder LSP handlers #26

retailcoder opened this issue Feb 24, 2023 · 0 comments
Assignees
Labels
component: Rubberduck.Client Issue involves RPC client/platform component: Server.LSP Issue involves the LSP server process feature: workspace explorer Issues that relate to the workspace explorer / sync panel skill:rpc Issues that involve StreamJsonRpc

Comments

@retailcoder
Copy link
Member

retailcoder commented Feb 24, 2023

The handlers themselves should go under Rubberduck.Client, which should have a namespace to keep the workspace handlers together (there will be more workspace handlers to implement in future sprints). Handlers should be injected with interfaces for the services they need, so these services need to have their interfaces in the same assembly, to be implemented under Rubberduck.Server.LSP.

@retailcoder retailcoder added component: Server.LSP Issue involves the LSP server process component: Rubberduck.Client Issue involves RPC client/platform skill:rpc Issues that involve StreamJsonRpc feature: workspace explorer Issues that relate to the workspace explorer / sync panel labels Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: Rubberduck.Client Issue involves RPC client/platform component: Server.LSP Issue involves the LSP server process feature: workspace explorer Issues that relate to the workspace explorer / sync panel skill:rpc Issues that involve StreamJsonRpc
Projects
None yet
Development

No branches or pull requests

2 participants