aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/config.ts
Commit message (Collapse)AuthorAgeFilesLines
* Introduce `toggle inlay hints` vscode commandveetaha2020-05-251-1/+1
| | | | | | | | Users now can assign a shortcut for this command via the general vscode keybindings ui or `keybinding.json file` Closes: #4599
* Add "rust-analyzer.lens.enable"vsrs2020-05-181-0/+2
|
* CodeLens configuration options.vsrs2020-05-171-0/+11
|
* Remove "rust-analyzer.debug.useLaunchJson" optionvsrs2020-05-141-2/+1
|
* Use launch.json in Debug Lens sessions.vsrs2020-05-131-0/+1
| | | | Add the possibility to use existing configurations via Debug Lens
* Merge remote-tracking branch 'upstream/master' into uniformed_debug_lensvsrs2020-05-081-0/+1
|\ | | | | | | | | # Conflicts: # editors/code/src/commands/runnables.ts
| * Add master config for inlayHints to make disabling easyAleksey Kladov2020-05-081-0/+1
| |
* | Add additional debug optionsvsrs2020-05-071-0/+2
| |
* | Uniformed way to get Debug Lens target executable.vsrs2020-05-061-2/+4
|/
* better configuration enum itemsvsrs2020-04-291-1/+1
|
* Configuration settings and source maps supportvsrs2020-04-291-1/+8
|
* Add config for proc_macroEdwin Cheng2020-04-161-0/+1
|
* vscode: fix typing bug in configveetaha2020-04-111-9/+30
|
* Enable the SemanticTokensFeature by defaultkjeremy2020-04-081-1/+0
| | | | | | | This is covered under vscode's "editor.semanticHighlighting.enabled" setting plus the user has to have a theme that has opted into highlighting. Bumps required vscode stable to 1.44
* Lean onto default implementation of configsAleksey Kladov2020-04-021-26/+4
|
* Remove old syntax highlightingAleksey Kladov2020-04-021-2/+0
|
* Process configuration response draftKirill Bulatov2020-03-301-3/+3
|
* vscode: fix local develveetaha2020-03-261-1/+1
| | | | The value of releaseTag is not undefined, but null in actual package.json
* Extension types and renderingMatt Hooper2020-03-241-0/+1
|
* Merge #3695bors[bot]2020-03-241-61/+45
|\ | | | | | | | | | | | | | | | | 3695: vscode: simplify and refactor config r=matklad a=Veetaha Removed unnecessary interfaces, changed `cfg` to be a getter to ensure the fresh values any time possible. Migrated from explicit casts to implicit. Co-authored-by: veetaha <[email protected]>
| * vscode: simplify and refactor configveetaha2020-03-231-61/+45
| |
* | Don't try to enable proposed API's on stableAleksey Kladov2020-03-241-12/+6
|/
* Make from-source install use cargo installed binary by defaultAleksey Kladov2020-03-201-2/+2
|
* Simplify extension tag sniffingAleksey Kladov2020-03-191-13/+7
|
* Rewrite auto-updateAleksey Kladov2020-03-191-96/+7
| | | | | | | | | | | | | | Everything now happens in main.ts, in the bootstrap family of functions. The current flow is: * check everything only on extension installation. * if the user is on nightly channel, try to download the nightly extension and reload. * when we install nightly extension, we persist its release id, so that we can check if the current release is different. * if server binary was not downloaded by the current version of the extension, redownload it (we persist the version of ext that downloaded the server).
* Remove outDirOverridesEmil Lauridsen2020-03-171-2/+0
|
* Change existing OUT_DIR override config to make use of new infrastructureEmil Lauridsen2020-03-171-1/+2
|
* Support loading OUT_DIR from cargo check at launchEmil Lauridsen2020-03-171-0/+3
|
* Separate persistent mutable state from configAleksey Kladov2020-03-161-41/+0
| | | | | That way, we clearly see which things are not change, and we also clearly see which things are persistent.
* vscode-postrefactor: more logging and better error handlingVeetaha2020-03-141-19/+17
|
* vscode-postrefactor: minor config refactoringsVeetaha2020-03-141-2/+3
|
* vscode-postrefactor: global storagesVeetaha2020-03-141-20/+19
|
* vscode: put comma backVeetaha2020-03-141-1/+1
|
* vscode: make bailing out on custom serverPath more evidentVeetaha2020-03-141-7/+5
|
* vscode: npm run fixVeetaha2020-03-141-3/+3
|
* vscode: prepare config for nightliesVeetaha2020-03-141-15/+96
|
* Merge #3543bors[bot]2020-03-121-3/+15
|\ | | | | | | | | | | | | | | | | | | | | | | | | 3543: Parameter inlay hint separate from variable type inlay? #2876 r=matklad a=slyngbaek Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side Co-authored-by: Steffen Lyngbaek <[email protected]>
| * Make maxLength nullable againSteffen Lyngbaek2020-03-121-2/+2
| |
| * Switch from Vec<InlayKind> to object with propsSteffen Lyngbaek2020-03-121-6/+7
| | | | | | | | | | | | | | - Instead of a single object type, use several individual nested types to allow toggling from the settings GUI - Remove unused struct definitions - Install and test that the toggles work
| * Address Issues from GithubSteffen Lyngbaek2020-03-101-1/+3
| | | | | | | | | | | | | | - Updated naming of config - Define struct in ra_ide and use remote derive in rust-analyzer/config - Make inlayConfig type more flexible to support more future types - Remove constructor only used in tests
| * Parameter inlay hint separate from variable type inlay? #2876Steffen Lyngbaek2020-03-101-2/+11
| | | | | | | | | | | | | | | | | | Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side
* | Add additional_outdirs in configEdwin Cheng2020-03-101-0/+1
|/
* vscode: groupd updates-related config under `updates` section as per @matkladVeetaha2020-03-091-1/+1
|
* vscode: fix inversion of askBeforeDownloadVeetaha2020-03-081-1/+1
|
* vscode: rename alwaysDownloadServer -> askBeforeDownloadVeetaha2020-03-081-1/+1
| | | | | | | | | | | The new name seems much simpler and it doesn't limit this config value only to downloading the server binary. Thus we wouldn't need to create another config properties to handle other downloads whatsoever. Anyway, I believe (heuristically) that most of the users would want to set "askBeforeDownload": false once and never bother clicking on the notification again (because otherwise there is no big point in installing rust-analyzer if it cannot install the server)
* vscode: care about alwaysDownloadServer option before askingVeetaha2020-03-071-5/+6
| | | | | | | Also renamed BinarySource to ArtifactSource in anticipation of nightlies installation that requires downloading not a binary itself but .vsix package, thus generalized to `artifact` term
* Config to switch to semantic tokensAleksey Kladov2020-02-261-0/+2
|
* Extract client-side loggingAleksey Kladov2020-02-221-1/+4
|
* Rename config value for server PathAleksey Kladov2020-02-181-1/+1
|
* Rename the binary to rust-analyzerAleksey Kladov2020-02-181-4/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 19:09:05 +0100