You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2023. It is now read-only.
I've read somewhere (can't find the place again) that there is (upcoming?) support for auto-formating RSX macro code, and displaying the documentation of RSX components and elements.
I guess, this functionality will only be available via the VSCode extension, and therefore I'd like to propose/suggest to implement it via a custom LSP server instead.
This way, these tools become automatically available to all editors/IDEs that support LSP (which are all relevant editors, I think).
Displaying documentation and auto-formating code is a subset of what Rust-Analyzer does, so there shouldn't be any technical limitation to implement the functionality via an LSP server. Helix has an open PR for adding support for several active LSP servers, so I guess other editors have that functionality, as well.
Rust seems to have good support for building custom LSP servers (see crates.io). For example, tower-lsp looks promising, and Rust-Analyzer uses lsp-types (tower-lsp as well).
I'm not 100% sure, if the LSP approach would work (I've never created an LSP server), but it would bring some significant benefits if it does (i.e., having one implementation of Dioxus IDE tool, that can be used by any editor/IDE).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I've read somewhere (can't find the place again) that there is (upcoming?) support for auto-formating RSX macro code, and displaying the documentation of RSX components and elements.
I guess, this functionality will only be available via the VSCode extension, and therefore I'd like to propose/suggest to implement it via a custom LSP server instead.
This way, these tools become automatically available to all editors/IDEs that support LSP (which are all relevant editors, I think).
Displaying documentation and auto-formating code is a subset of what Rust-Analyzer does, so there shouldn't be any technical limitation to implement the functionality via an LSP server. Helix has an open PR for adding support for several active LSP servers, so I guess other editors have that functionality, as well.
Rust seems to have good support for building custom LSP servers (see crates.io). For example, tower-lsp looks promising, and Rust-Analyzer uses lsp-types (
tower-lsp
as well).I'm not 100% sure, if the LSP approach would work (I've never created an LSP server), but it would bring some significant benefits if it does (i.e., having one implementation of Dioxus IDE tool, that can be used by any editor/IDE).
The text was updated successfully, but these errors were encountered: