Closed Savio-Sou closed 8 months ago
@kobyhallx brought up the point that this could require either:
To discuss further on how to approach the problem. cc @kevaundray
To clarify
Refactoring of the entire LSP codebase
we would refactor LSP parts, server interactions etc, while still relying on wasm module bringing in functionality developed so far in Rust related to compilation process.
@Savio-Sou The usecase for this was so that developers did not need to set up their environment at in-person workshops/events. Dev containers are easier to implement so we are going with that and putting this low on the priority list. (It's still unclear if we ever need to implement this)
The priority right now is to implement the features needed in the LSP -- I've already CC'd with @kobyhallx earlier this week regarding implementing go to definition.
Also, the point of this was to do this in js so we enable better contracts for js based tooling. Doing this with the browser's first mindset was rather a bonus rather than a goal by itself.
Closing this as its no longer relevant, given we have codespaces
Problem
When a user opens a GitHub repository through https://github.dev/ and attempts to install the Noir Language Support extension in it, he/she would be prompted with:
Happy Case
As a Noir developer, I want to use the extension in the manner of:
so that I can easily view, write and debug Noir programs in web browsers.
Alternatives Considered
As an MVP, we could support a subset (instead of full set) of features in step (5) above.
Additional Context
VS Code for the Web
Would you like to submit a PR for this Issue?
No
Support Needs
No response