From ddfac09363fa778e3830cdb7a9ce6de3d779072e Mon Sep 17 00:00:00 2001 From: Aleksey Kladov Date: Thu, 12 Mar 2020 18:04:11 +0100 Subject: Fix docs --- docs/user/features.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/user/features.md b/docs/user/features.md index 06bc7ded5..45360c633 100644 --- a/docs/user/features.md +++ b/docs/user/features.md @@ -191,8 +191,9 @@ Two types of inlay hints are displayed currently: In VS Code, the following settings can be used to configure the inlay hints: -* `rust-analyzer.inlayHintOpts.displayType` configure which types of inlay hints are shown. -* `rust-analyzer.inlayHintOpts.maxLength` — shortens the hints if their length exceeds the value specified. If no value is specified (`null`), no shortening is applied. +* `rust-analyzer.inlayHints.typeHints` - enable hints for inferred types. +* `rust-analyzer.inlayHints.parameterHints` - enable hints for function parameters. +* `rust-analyzer.inlayHints.maxLength` — shortens the hints if their length exceeds the value specified. If no value is specified (`null`), no shortening is applied. **Note:** VS Code does not have native support for inlay hints [yet](https://github.com/microsoft/vscode/issues/16221) and the hints are implemented using decorations. This approach has limitations, the caret movement and bracket highlighting near the edges of the hint may be weird: -- cgit v1.2.3