aboutsummaryrefslogtreecommitdiff
path: root/docs/user/generated_config.adoc
Commit message (Collapse)AuthorAgeFilesLines
* Implement a config override for the default #[cfg(test)] in cargo cratesJade2021-06-191-0/+5
| | | | | | | | Fixes crates which vanish when the 'test' cfg atom is set. Fix #7243. Fix #9203. Fix #7225.
* Allow to disable import insertion on single path glob importsLukas Wirth2021-06-181-0/+5
|
* Add function references hover actionLukas Wirth2021-06-041-0/+6
|
* Make it opt-inJonas Schievink2021-06-031-0/+5
|
* Document that `addCallArgumentSnippets` requires `addCallParenthesisLukas Wirth2021-06-021-0/+1
|
* Add config setting for self-on-the-flyLukas Wirth2021-05-311-0/+6
|
* Fix incorrect setting descriptionsLucas Schwiderski2021-05-291-6/+6
| | | | | | | | Descriptions for diagnostic warning hint and info display were swapped. Fixes #8485. Signed-off-by: Lucas Schwiderski <[email protected]>
* implement range formattingAndy Russell2021-05-231-0/+7
|
* Merge #8873bors[bot]2021-05-201-2/+7
|\ | | | | | | | | | | | | | | | | | | | | | | 8873: Implement import-granularity guessing r=matklad a=Veykril This renames our `MergeBehavior` to `ImportGranularity` as rustfmt has it as the purpose of them are basically the same. `ImportGranularity::Preserve` currently has no specific purpose for us as we don't have an organize imports assist yet, so it currently acts the same as `ImportGranularity::Item`. We now try to guess the import style on a per file basis and fall back to the user granularity setting if the file has no specific style yet or where it is ambiguous. This can be turned off by setting `import.enforceGranularity` to `true`. Closes https://github.com/rust-analyzer/rust-analyzer/issues/8870 Co-authored-by: Lukas Tobias Wirth <[email protected]>
| * Replace ImportGranularity::Guess with guessing boolean flagLukas Tobias Wirth2021-05-191-2/+7
| |
* | Add new LSP extension for workspace symbol lookupalcroito2021-05-171-0/+10
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new extension allows filtering of workspace symbool lookup results by search scope or search kind. Filtering can be configured in 3 different ways: - The '#' or '*' markers can be added inline with the symbol lookup query. The '#' marker means symbols should be looked up in the current workspace and any dependencies. If not specified, only current workspace is considered. The '*' marker means all kinds of symbols should be looked up (types, functions, etc). If not specified, only type symbols are returned. - Each LSP request can take an optional search_scope or search_kind argument query parameter. - Finally there are 2 global config options that can be set for all requests served by the active RA instance. Add support for setting the global config options to the VSCode extension. The extension does not use the per-request way, but it's useful for other IDEs. The latest version of VSCode filters out the inline markers, so currently the only reasonable way to use the new functionality is via the global config.
* minor: adjust config nameAleksey Kladov2021-05-171-9/+9
|
* Merge #8795bors[bot]2021-05-171-0/+9
|\ | | | | | | | | | | | | | | | | | | 8795: Allow semantic tokens for strings to be disabled r=matklad a=djrenren Fixes https://github.com/rust-analyzer/rust-analyzer/issues/7111 Pretty straightforward change, but open to any suggestions if there's a more recommended testing strategy than what I went with. Co-authored-by: John Renner <[email protected]>
| * Formatting and docsJohn Renner2021-05-101-0/+9
| |
* | Update docsLukas Wirth2021-05-101-1/+1
|/
* internal: ensure that client and server-side configs are not mixed upAleksey Kladov2021-04-281-5/+0
| | | | https://github.com/rust-lang/rust/issues/84647 would help big time here.
* Add config optionsJorge Mederos Alvarado2021-04-271-0/+5
|
* Code review feedback.James Leitch2021-04-211-2/+2
|
* Diagnostic Remap Path Prefixes added.James Leitch2021-04-211-0/+6
|
* feat: avoid checking the whole project during initial loadingAleksey Kladov2021-04-121-0/+6
|
* Bump the default hint lengthKirill Bulatov2021-03-231-1/+1
|
* Limit the hints size by defaultKirill Bulatov2021-03-231-2/+2
|
* Enable proc-macros by defaultAleksey Kladov2021-03-151-1/+1
|
* Make code less surprisingAleksey Kladov2021-03-091-57/+265
| | | | Theres no reason to have literal `\n\n` in the source code
* Add more documentation for rustc_privateJoshua Nelson2021-03-081-1/+1
|
* Merge #7891bors[bot]2021-03-081-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7891: Improve handling of rustc_private r=matklad a=DJMcNab This PR changes how `rust-analyzer` handles `rustc_private`. In particular, packages now must opt-in to using `rustc_private` in `Cargo.toml`, by adding: ```toml [package.metadata.rust-analyzer] rustc_private=true ``` This means that depending on crates which also use `rustc_private` will be significantly improved, since their dependencies on the `rustc_private` crates will be resolved properly. A similar approach could be used in #6714 to allow annotating that your package uses the `test` crate, although I have not yet handled that in this PR. Additionally, we now only index the crates which are transitive dependencies of `rustc_driver` in the `rustcSource` directory. This should not cause any change in behaviour when using `rustcSource: "discover"`, as the source used then will only be a partial clone. However, if `rustcSource` pointing at a local checkout of rustc, this should significantly improve the memory usage and lower indexing time. This is because we avoids indexing all crates in `src/tools/`, which includes `rust-analyzer` itself. Furthermore, we also prefer named dependencies over dependencies from `rustcSource`. This ensures that feature resolution for crates which are depended on by both `rustc` and your crate uses the correct set for analysing your crate. See also [introductory zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Fixed.20crate.20graphs.20and.20optional.20builtin.20crates/near/229086673) I have tested this in [priroda](https://github.com/oli-obk/priroda/), and it provides a significant improvement to the development experience (once I give `miri` the required data in `Cargo.toml`) Todo: - [ ] Documentation This is ready to review, and I will add documentation if this would be accepted (or if I get time to do so anyway) Co-authored-by: Daniel McNab <[email protected]>
| * Document rustc_private in metadataDaniel McNab2021-03-081-1/+1
| |
| * Revert "Support disabling rustc build scripts"Daniel McNab2021-03-081-2/+0
| | | | | | | | This reverts commit ddce6bb282764692d53b719bff4c37e3512d4556.
| * Support disabling rustc build scriptsDaniel McNab2021-03-081-0/+2
| |
* | Make code completion "just work" in more casesAleksey Kladov2021-03-081-1/+1
| |
* | Make group imports configurableasv2021-03-071-0/+2
|/
* Migrate to user-centric config name for `cargo check` stuffAleksey Kladov2021-03-041-3/+3
|
* Allow automatically detect the rustc-src directory (fixes #3517).Benjamin Bouvier2021-02-131-1/+1
| | | | | If the configured rustcSource is set to "discover", try to automatically detect a source from the sysroot rustc directory.
* Add config option to ignore directoriesAleksey Kladov2021-01-261-0/+2
|
* Remove the need to manually sync config in package.jsonAleksey Kladov2021-01-261-4/+4
|
* Add References code lens.vsrs2021-01-231-0/+2
| | | | For Struct, Enum, Union and Trait symbols.
* Use american spelling for configAleksey Kladov2021-01-071-1/+1
| | | | | | | | As per https://github.com/rust-analyzer/rust-analyzer/blob/171c3c08fe245938fb25321394233de5fe2abc7c/docs/dev/style.md#variable-naming Also implement config aliasing, for pain-free settings migrations in the future
* More maintainable configAleksey Kladov2021-01-061-0/+2
| | | | | | | Rather than eagerly converting JSON, we losslessly keep it as is, and change the shape of user-submitted data at the last moment. This also allows us to remove a bunch of wrong Defaults
* Allow `#anchor` linking of config optionsAleksey Kladov2021-01-051-53/+53
|
* Clean up descriptions for settingsRüdiger Herrmann2020-12-221-13/+13
| | | | | | | | | | | | Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
* Include config into the manualAleksey Kladov2020-12-091-0/+106
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 17:14:53 +0000