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

📎 IntelliJ Platform LSP #93

Closed
Conaclos opened this issue Aug 30, 2023 · 3 comments · Fixed by #185
Closed

📎 IntelliJ Platform LSP #93

Conaclos opened this issue Aug 30, 2023 · 3 comments · Fixed by #185
Assignees
Labels
A-LSP Area: language server protocol S-Help-wanted Status: you're familiar with the code base and want to help the project

Comments

@Conaclos
Copy link
Member

Conaclos commented Aug 30, 2023

Description

Implement lsp client for IntelliJ.

Some preliminary works were previously done. In particular an implementation.

@Conaclos Conaclos changed the title 📎 IntelliJ Platform Language Server Protocol 📎 IntelliJ Platform LSP Aug 30, 2023
@Conaclos Conaclos added A-LSP Area: language server protocol S-Help-wanted Status: you're familiar with the code base and want to help the project labels Aug 30, 2023
@victor-teles
Copy link
Contributor

victor-teles commented Sep 3, 2023

@Conaclos Can i help with this one? what are the basic functionalities needed?

  • Formatting
  • Linting
  • Automatic restart LSP when biome.json change and settings changes
  • Automatic find biome binary in node_modules
  • Statusbar widget same as vscode Biome ${version}
  • Toolbar action for restart server

Anything else?

The code need to be in this repository?

@ematipico
Copy link
Member

Thank you @victor-teles

Here's something to start with: https://blog.jetbrains.com/platform/2023/07/lsp-for-plugin-developers/

The blog post says only four events are supported. Biome would be able to support only textDocument/codeAction and textDocument/publishDiagnostics. So no formatting for the time being.

The code has to live in the repository, inside the editors/ directory. It would be great to also have, for us developers:

  • instructions for local development;
  • setting to change the path of the binary;

Eventually, extend the publishing workflow, to include this new plugin.

@victor-teles
Copy link
Contributor

@ematipico alright, can you assign it to me ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-LSP Area: language server protocol S-Help-wanted Status: you're familiar with the code base and want to help the project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants