As originally referenced in this issue :
As described in the rust-analyzer codebase here, as far as I could find, there is no way for the lsp client to set rust-analyzer.completion.snippets.custom to allow for some custom snippet that would hook into rust-analyzer's parsing.
I imagine that it would mean adding a new variable here :
|
(lsp-register-custom-settings |
|
'(("rust.show_hover_context" lsp-rust-show-hover-context t) |
|
("rust.full_docs" lsp-rust-full-docs t) |
|
("rust.build_command" lsp-rust-build-command) |
|
("rust.rustfmt_path" lsp-rust-rustfmt-path) |
|
("rust.target_dir" lsp-rust-target-dir) |
|
("rust.all_targets" lsp-rust-all-targets t) |
|
("rust.jobs" lsp-rust-jobs) |
|
("rust.clippy_preference" lsp-rust-clippy-preference) |
|
("rust.racer_completion" lsp-rust-racer-completion t) |
|
("rust.no_default_features" lsp-rust-no-default-features t) |
|
("rust.all_features" lsp-rust-all-features t) |
|
("rust.features" lsp-rust-features) |
|
("rust.build_on_save" lsp-rust-build-on-save t) |
|
("rust.crate_blocklist" lsp-rust-crate-blocklist) |
|
("rust.show_warnings" lsp-rust-show-warnings t) |
|
("rust.wait_to_build" lsp-rust-wait-to-build) |
|
("rust.unstable_features" lsp-rust-unstable-features t) |
|
("rust.cfg_test" lsp-rust-cfg-test t) |
|
("rust.build_bin" lsp-rust-build-bin) |
|
("rust.build_lib" lsp-rust-build-lib t) |
|
("rust.clear_env_rust_log" lsp-rust-clear-env-rust-log t) |
|
("rust.rustflags" lsp-rust-rustflags) |
|
("rust.target" lsp-rust-target) |
|
("rust.sysroot" lsp-rust-sysroot))) |
Would gladly make a pull request with guidance
