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

[Bug Tracking] LSP (VS Code) #763

Open
ankitaS11 opened this issue Jul 14, 2022 · 2 comments
Open

[Bug Tracking] LSP (VS Code) #763

ankitaS11 opened this issue Jul 14, 2022 · 2 comments

Comments

@ankitaS11
Copy link
Collaborator

ankitaS11 commented Jul 14, 2022

This issue will contain discussions and bug tracking around LSP support for VSCode.

@certik
Copy link
Contributor

certik commented Jul 19, 2022

TODO:

  • fix bugs (sometimes it doesn't seem to update / clean error messages when saved)
  • the symbol table gets duplicated
  • Implement symbol lookup (F12)
  • add tests (add a Python script that launches "lpython lsp ..." and sends JSON to it, and checks that a correct JSON gets returned)
  • document in README how to test the LSP (how to compile the extension and test it out in Debug mode)
  • polish the extension, move it under lcompilers/lpython_vscode_extension (or something like that), and publish on VSCode marketplace
  • Figure out how to make it work "automatically", without the need to save (?)
  • Add a "Debug" button, that would expose all AST and ASR nodes in the "Outline", which would be helpful for Debugging and ensuring the AST and ASR is correct; in fact we can even expose the ASR and Python source code (?) after each ASR pass, so that we can visually ensure that it is correct (this would be very helpful for developing ASR passes such as optimizations)
  • Add a "Run" button that would compile and run the current file

@certik
Copy link
Contributor

certik commented Jul 19, 2022

Here is the current state:

  • Errors get highlighted (when you save with Ctrl-S)
  • The file symbols (from ASR) get shown in the Outline

Screen Shot 2022-07-19 at 2 29 02 PM

@certik certik pinned this issue Jul 19, 2022
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