Skip to content

Commit 71a4ed3

Browse files
Add ".enable" after rescript.settings.codeLens in documentation
1 parent e3700a3 commit 71a4ed3

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
#### :rocket: New Feature
1616

1717
- Inlay Hints (experimetal). `rescript.settings.inlayHints.enable: true`. Turned off by default. https://github.com/rescript-lang/rescript-vscode/pull/453
18-
- Code Lenses for functions (experimetal). `rescript.settings.codeLens: true`. Turned off by default. https://github.com/rescript-lang/rescript-vscode/pull/513
18+
- Code Lenses for functions (experimetal). `rescript.settings.codeLens.enable: true`. Turned off by default. https://github.com/rescript-lang/rescript-vscode/pull/513
1919
- Markdown code blocks tagged as `rescript` now get basic syntax highlighting. https://github.com/rescript-lang/rescript-vscode/pull/97
2020
- Hover support for doc comments on v10 compiler `/** this is a doc comment */`
2121

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ You'll find all ReScript specific settings under the scope `rescript.settings`.
107107
| Prompt to Start Build | If there's no ReScript build running already in the opened project, the extension will prompt you and ask if you want to start a build automatically. You can turn off this automatic prompt via the setting `rescript.settings.askToStartBuild`. |
108108
| ReScript Binary Path | The extension will look for the existence of a `/node_modules/.bin/rescript` file and use its directory as the `binaryPath`. If it does not find it at the project root (which is where the nearest `bsconfig.json` resides), it goes up folders in the filesystem recursively until it either finds it (often the case in monorepos) or hits the top level. To override this lookup process, the path can be configured explicitly using the setting `rescript.settings.binaryPath` |
109109
| Inlay Hints (experimental) | This allows an editor to place annotations inline with text to display type hints. Enable using `rescript.settings.inlayHints.enable: true` |
110-
| Code Lens (experimental) | This tells the editor to add code lenses to function definitions, showing its full type above the definition. Enable using `rescript.settings.codeLens: true` |
110+
| Code Lens (experimental) | This tells the editor to add code lenses to function definitions, showing its full type above the definition. Enable using `rescript.settings.codeLens.enable: true` |
111111
| Autostarting the Code Analyzer | The Code Analyzer needs to be started manually by default. However, you can configure the extension to start the Code Analyzer automatically via the setting `rescript.settings.autoRunCodeAnalysis`. |
112112

113113
**Default settings:**
@@ -129,7 +129,7 @@ You'll find all ReScript specific settings under the scope `rescript.settings`.
129129
"rescript.settings.inlayHints.maxLength": 25
130130

131131
// Enable (experimental) code lens for function definitions.
132-
"rescript.settings.codeLens": true
132+
"rescript.settings.codeLens.enable": true
133133
```
134134

135135
## 🚀 Code Analyzer

0 commit comments

Comments
 (0)