| Age | Commit message (Collapse) | Author | Lines |
|
|
|
Improve settings tree title and descriptions
|
|
|
|
|
|
Bumps [form-data](https://github.com/form-data/form-data) from 4.0.2 to 4.0.4.
- [Release notes](https://github.com/form-data/form-data/releases)
- [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md)
- [Commits](https://github.com/form-data/form-data/compare/v4.0.2...v4.0.4)
---
updated-dependencies:
- dependency-name: form-data
dependency-version: 4.0.4
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
- All settings are now phrased in the imperative form stating what the
setting does rather than talking about what it controls. (E.g.:
"Show `Debug` action." instead of "Whether to show `Debug` action"
- Categories are now displayed in title case
- Categories are now sorted lexicographically
- General category is removed (and all the settings are moved to the top
level)
- Language for a few descriptions is made a bit less ambiguous
|
|
Cleanup `provideCodeActions` vscode hook
|
|
|
|
|
|
`match`, `if`, or match arm arrow (`=>`)
|
|
feat: Extend vscode 'run' command with optional mode argument for run…
|
|
main.createCommands instead
|
|
test(s) or bin at keyboard cursor
|
|
|
|
|
|
|
|
feat: In "Fill match arms", allow users to prefer `Self` to the enum name when possible
|
|
|
|
|
|
Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 1.1.11 to 1.1.12.
- [Release notes](https://github.com/juliangruber/brace-expansion/releases)
- [Commits](https://github.com/juliangruber/brace-expansion/compare/1.1.11...v1.1.12)
---
updated-dependencies:
- dependency-name: brace-expansion
dependency-version: 1.1.12
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
possible
But default to not to.
I chose to have a more generic config name because maybe other assists could also use the same approach.
|
|
Bumps [tar-fs](https://github.com/mafintosh/tar-fs) from 2.1.2 to 2.1.3.
- [Commits](https://github.com/mafintosh/tar-fs/commits)
---
updated-dependencies:
- dependency-name: tar-fs
dependency-version: 2.1.3
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
The current default plain, tends to create non-uniform import blocks over time, some being relative, some being absolute.
I believe we should encourage a different default here.
|
|
Bumps [undici](https://github.com/nodejs/undici) from 6.21.1 to 6.21.3.
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](https://github.com/nodejs/undici/compare/v6.21.1...v6.21.3)
---
updated-dependencies:
- dependency-name: undici
dependency-version: 6.21.3
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
Also first line of default code blocks being used as the language instead of json
and fixes a missing `json` language in a doc comment code block.
|
|
|
|
|
|
|
|
|
|
A Cargo project can now be built without any dependency metadata being fetched.
Signed-off-by: Prajwal S N <prajwalnadig21@gmail.com>
|
|
|
|
- Fix #18782
|
|
|
|
|
|
We register the provider when we start the server. It confused me why I set the option and it didn't work, so probably better to have it hint people.
|
|
|
|
Allow unsetting default cfgs
|
|
|
|
|
|
|
|
Also fix the `needs_drop()` intrinsic.
Unions also need this information (to err if they have a drop-needing field), but this will come in a follow-up PR.
|
|
|
|
rust-lang/dependabot/npm_and_yarn/editors/code/esbuild-0.25.0
Bump esbuild from 0.18.12 to 0.25.0 in /editors/code
|
|
fix: Make `rust-analyzer.files.excludeDirs` work, actually
|
|
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.18.12 to 0.25.0.
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md)
- [Commits](https://github.com/evanw/esbuild/compare/v0.18.12...v0.25.0)
---
updated-dependencies:
- dependency-name: esbuild
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
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.
|