about summary refs log tree commit diff
path: root/src/tools/rust-analyzer/docs
AgeCommit message (Collapse)AuthorLines
2025-02-12manual: Separate out installation and configuration pagesWilfred Hughes-618/+635
Organise the installation content into: * VS Code instructions * Binary installation * Editor configuration
2025-02-12Merge pull request #18928 from roife/fix-18918Lukas Wirth-0/+5276
fix: handle character boundary in search mode
2025-02-12fix: handle character boundary in search moderoife-0/+5276
2025-02-12Merge pull request #19132 from joshrotenberg/book-readme-run-codegenLukas Wirth-1/+1
doc: add xtask codegen command in development README as well
2025-02-11remove unused plugin configJosh Rotenberg-5/+0
2025-02-11Merge pull request #19133 from joshrotenberg/fix-manual-github-pathsChayim Refael Friedman-3/+3
doc: fix mdbook repository paths
2025-02-11Merge pull request #18998 from ChayimFriedman2/excludeLukas Wirth-2/+2
fix: Make `rust-analyzer.files.excludeDirs` work, actually
2025-02-10fix mdbook pathsJosh Rotenberg-3/+3
2025-02-10add xtask codegen command as wellJosh Rotenberg-1/+1
2025-02-09doc: error url阿豪-1/+1
2025-02-07Organise chapters in mdbook sidebarWilfred Hughes-3/+3
2025-02-06closure parameter inlay hintsjnyfah-0/+5
2025-02-04Make `rust-analyzer.files.excludeDirs` work, actuallyChayim Refael Friedman-2/+2
I have no idea what the original writer of the code thought but the logic just seems backwards. We should not exclude a file/directory if it is equal to an include! This also meant that we had to add a `root == path` check so this stuff will actually work, which in turn meant excludes (of root files) no longer worked... Also rename if to `rust-analyzer.files.exclude`, because it can exclude files as well.
2025-01-28Merge pull request #19015 from Wilfred/mdbookLukas Wirth-2321/+2563
manual: Convert to mdbook
2025-01-26Update outdated permissions section in the README.mdLukas Wirth-12/+6
2025-01-25Skip redundant path search in `resolve_completion_edits`Lukas Wirth-1/+1
2025-01-24manual: Convert to mdbookWilfred Hughes-2321/+2563
Split manual.adoc into markdown files, one for each chapter. For the parts of the manual that are generated from source code doc comments, update the comments to use markdown syntax and update the code generators to write to `generated.md` files. For the weekly release, stop copying the .adoc files to the `rust-analyzer/rust-analyzer.github.io` at release time. Instead, we'll sync the manual hourly from this repository. See https://github.com/rust-analyzer/rust-analyzer.github.io/pull/226 for the sync. This PR should be merged first, and that PR needs to be merged before the next weekly release. This change is based on #15795, but rebased and updated. I've also manually checked each page for markdown syntax issues and fixed any I encountered. Co-authored-by: Lukas Wirth <lukastw97@gmail.com> Co-authored-by: Josh Rotenberg <joshrotenberg@gmail.com>
2025-01-24Merge pull request #18993 from ChayimFriedman2/iter-configLukas Wirth-0/+10
feat: Provide a config to control auto-insertion of `await` and `iter()`
2025-01-21manual: Document all rust-project.json fieldsWilfred Hughes-7/+83
Ensure that all the fields that rust-analyzer understands are in the manual, they all have doc comments, and they use consistent punctuation (`;` rather than mixing `,` and `;`). Whilst we're here, fix the `sysroot_src` example and add 2024 as a legal value for Rust edition.
2025-01-21Provide a config to control auto-insertion of `await` and `iter()`Chayim Refael Friedman-0/+10
2025-01-17Update syntax tree viewer docsMark Murphy-7/+9
2025-01-16Fix `debug_assertions` broken in 1c5a125beb35725ccc2ade005db9870db734bf23VinTarZ-1/+1
2025-01-15Flip on typing config to be opt-in, better defaultsLukas Wirth-4/+12
2025-01-10Implement implicit sized bound inlay hintsLukas Wirth-0/+5
2025-01-10Merge pull request #18813 from Giga-Bowser/syntax-tree-viewLukas Wirth-1/+18
feat: Add a new and improved syntax tree view
2025-01-09Remove the old syntax tree viewerGiga Bowser-1/+1
2025-01-09Add a new and improved syntax tree viewerGiga Bowser-1/+18
2025-01-09Merge pull request #18880 from PrototypeNM1/extra-includesLukas Wirth-0/+7
Add config setting which allows adding additional include paths to the VFS.
2025-01-08Add config setting which allows adding additional include paths to the VFS.Nicholas Rishel-0/+7
2025-01-08fix: autogenerate filesqjerome-4/+4
2025-01-07target-triple -> target-tupleLukas Wirth-2/+2
2025-01-07Remove `rust-analyzer.cargo.sysrootQueryMetadata` config againLukas Wirth-6/+0
2025-01-06fix: Be more permissive with completion resolve dataLukas Wirth-1/+1
2025-01-01Merge pull request #18179 from ChayimFriedman2/omit-trait-completionLukas Wirth-0/+38
feat: Allow excluding specific traits from completion
2025-01-01Revamp auto-import exclude configLukas Wirth-5/+16
2025-01-01Reduce the default autoimport exclusion listLukas Wirth-40/+3
2025-01-01Allow excluding specific traits from completionChayim Refael Friedman-0/+64
To be accurate, only their methods are excluded, the trait themselves are still available. I also excluded a bunch of std traits by default. Some less opinionated, like `AsRef`, which should never be used directly except in generic scenarios (and won't be excluded there), some more opinionated, like the ops traits, which I know some users sometimes want to use directly. Either way it's configurable. It should be pretty easy to extend support to excluding only specific methods, but I didn't do that currently. Traits configured to be excluded are resolved in each completion request from scratch. If this proves too expensive, it is easy enough to cache them in the DB.
2024-12-26fix incorrect name for UpdateTest configroife-1/+1
2024-12-26feat: add config `UpdateTest` to hover actionsroife-0/+6
2024-12-26feat: support UpdateTest in codelensroife-1/+7
2024-12-24Merge pull request #18707 from ChayimFriedman2/substLukas Wirth-0/+9
feat: Show substitution where hovering over generic things
2024-12-22fix: Properly check if workspace flychecking is allowedLukas Wirth-1/+2
2024-12-20Show substitution where hovering over generic thingsChayim Refael Friedman-0/+9
There are few things to note in the implementation: First, this is a best-effort implementation. Mainly, type aliases may not be shown (due to their eager nature it's harder) and partial pathes (aka. hovering over `Struct` in `Struct::method`) are not supported at all. Second, we only need to show substitutions in expression and pattern position, because in type position all generic arguments always have to be written explicitly.
2024-12-16internal: Don't serialize empty fields in completions and resolve payloadsLukas Wirth-1/+1
2024-12-11Fix publish workflow link in manualSam Estep-1/+1
2024-12-10Address the feedback from pascalkutheKirill Bulatov-1/+1
* Use Base64 to minify the hash representation in the JSON data * Do hash checks only for items with similar labels
2024-12-09Always compute the hash when r-a wants the imports to be resolvedKirill Bulatov-1/+1
2024-12-09Draft completion hashingKirill Bulatov-1/+1
2024-12-09Disable pipe on typing handlerLukas Wirth-1/+1
2024-12-06Add typing handler for param list pipeLukas Wirth-2/+2