mirrors/zed
1
0
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2024-12-26 10:40:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8
zed/.zed/settings.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

50 lines
982 B
JSON
Raw Normal View History

Ensure json uses a tab size of 4
2023-07-31 17:08:40 +00:00
{
Fix `Cargo.toml` formatting (#7886) This PR disables the formatting for `.toml` files within the Zed repo, as the formatter provided by the TOML language server messes things up. Release Notes: - N/A
2024-02-16 02:54:43 +00:00
"languages": {
Adjust tab size for Markdown (#8079) This PR sets the `tab_size` for Markdown to 2 spaces. This should prevent Prettier from adding a bunch of leading whitespace when formatting Markdown lists. Release Notes: - N/A
2024-02-20 18:15:14 +00:00
"Markdown": {
"tab_size": 2,
"formatter": "prettier"
},
Fix `Cargo.toml` formatting (#7886) This PR disables the formatting for `.toml` files within the Zed repo, as the formatter provided by the TOML language server messes things up. Release Notes: - N/A
2024-02-16 02:54:43 +00:00
"TOML": {
"formatter": "prettier",
"format_on_save": "off"
Format YAML files (#7887) This PR formats the YAML files in the repo with Prettier. Release Notes: - N/A
2024-02-16 03:04:57 +00:00
},
"YAML": {
Ensure more Zed files are formatted uniformly (#8505) Follow-up of https://github.com/zed-industries/zed/pull/8500#issuecomment-1967522477 Now things are much better, but I still reformat the default.json settings file: ```diff diff --git a/assets/settings/default.json b/assets/settings/default.json index c60c53026..67bf4505b 100644 --- a/assets/settings/default.json +++ b/assets/settings/default.json @@ -75,14 +75,7 @@ // Hide the values of in variables from visual display in private files "redact_private_values": false, // Globs to match against file paths to determine if a file is private. - "private_files": [ - "**/.env*", - "**/*.pem", - "**/*.key", - "**/*.cert", - "**/*.crt", - "**/secrets.yml" - ], + "private_files": ["**/.env*", "**/*.pem", "**/*.key", "**/*.cert", "**/*.crt", "**/secrets.yml"], // Whether to use additional LSP queries to format (and amend) the code after // every "trigger" symbol input, defined by LSP server capabilities. "use_on_type_format": true, ``` For me, Zed's doing that with the default prettier: ``` ['/Users/someonetoignore/work/zed/zed/assets/settings/default.json' with options: {"printWidth":120,"tabWidth":2,"parser":"json","plugins":[],"path":"/Users/someonetoignore/work/zed/zed/assets/settings/default.json"}](stderr: Resolved config: {}, will format file '/Users/someonetoignore/work/zed/zed/assets/settings/default.json' with options: {"printWidth":120,"tabWidth":2,"parser":"json","plugins":[],"path":"/Users/someonetoignore/work/zed/zed/assets/settings/default.json"}) ``` and `!/Library/Application Support/Zed/prettier/package-lock.json` states that I have ``` "node_modules/prettier": { "version": "3.2.5", "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.2.5.tgz", "integrity": "sha512-3/GWa9aOC0YeD7LUfvOG2NiDyhOWRvt1k+rcKhOuYnMY24iiCphgneUfJDyFXd6rZCAnuLBv6UeAULtrhT/F4A==", "bin": { "prettier": "bin/prettier.cjs" }, "engines": { "node": ">=14" }, "funding": { "url": "https://github.com/prettier/prettier?sponsor=1" } }, ``` Release Notes: - N/A
2024-02-27 21:25:36 +00:00
"tab_size": 2,
"formatter": "prettier"
},
"JSON": {
"tab_size": 2,
Keymap oneliners (#13887) This is should be a no-op, whitespace formatting only. Removes 425 lines of excess whitespace in our default keymap json files. Release Notes: - Improved formatting of default keymaps (single line per bind)
2024-07-06 02:00:18 +00:00
"preferred_line_length": 100,
Format YAML files (#7887) This PR formats the YAML files in the repo with Prettier. Release Notes: - N/A
2024-02-16 03:04:57 +00:00
"formatter": "prettier"
Keymap oneliners (#13887) This is should be a no-op, whitespace formatting only. Removes 425 lines of excess whitespace in our default keymap json files. Release Notes: - Improved formatting of default keymaps (single line per bind)
2024-07-06 02:00:18 +00:00
},
"JSONC": {
Format `prettier_server.js` (#9583) This PURELY formats the file by opening it in Zed and hitting save with save-on-format on. It's been bugging me that I can't change the file without the whole thing getting reformatted, so here we are. Release Notes: - N/A
2024-03-20 18:49:14 +00:00
"tab_size": 2,
Keymap oneliners (#13887) This is should be a no-op, whitespace formatting only. Removes 425 lines of excess whitespace in our default keymap json files. Release Notes: - Improved formatting of default keymaps (single line per bind)
2024-07-06 02:00:18 +00:00
"preferred_line_length": 100,
Format YAML files (#7887) This PR formats the YAML files in the repo with Prettier. Release Notes: - N/A
2024-02-16 03:04:57 +00:00
"formatter": "prettier"
Format `prettier_server.js` (#9583) This PURELY formats the file by opening it in Zed and hitting save with save-on-format on. It's been bugging me that I can't change the file without the whole thing getting reformatted, so here we are. Release Notes: - N/A
2024-03-20 18:49:14 +00:00
},
"JavaScript": {
"tab_size": 2,
"formatter": "prettier"
tasks: Add experimental support for user-defined task variables (#13699) Context: @bennetbo spotted a regression in handling of `cargo run` task in zed repo following a merge of #13658. We've started invoking `cargo run` from the folder of an active file whereas previously we did it from the workspace root. We brainstormed few solutions that involved adding a separate task that gets invoked at a workspace level, but I realized that a cleaner solution may be to finally add user-configured task variables. This way, we can choose which crate to run by default at a workspace level. This has been originally brought up in the context of javascript tasks in https://github.com/zed-industries/zed/pull/12118#issuecomment-2129232114 Note that this is intended for internal use only for the time being. /cc @RemcoSmitsDev we should be unblocked on having runner-dependant tasks now. Release notes: - N/A
2024-07-01 13:59:19 +00:00
},
docs: Format CSS with Prettier (#15333) This PR formats the CSS in the docs with Prettier. The indentation of these CSS files kept changing based on who last touched them, so I added settings to the Zed repo to try and keep the formatting intact until we can enforce it in CI. Release Notes: - N/A
2024-07-27 14:25:51 +00:00
"CSS": {
"tab_size": 2,
"formatter": "prettier"
},
tasks: Add experimental support for user-defined task variables (#13699) Context: @bennetbo spotted a regression in handling of `cargo run` task in zed repo following a merge of #13658. We've started invoking `cargo run` from the folder of an active file whereas previously we did it from the workspace root. We brainstormed few solutions that involved adding a separate task that gets invoked at a workspace level, but I realized that a cleaner solution may be to finally add user-configured task variables. This way, we can choose which crate to run by default at a workspace level. This has been originally brought up in the context of javascript tasks in https://github.com/zed-industries/zed/pull/12118#issuecomment-2129232114 Note that this is intended for internal use only for the time being. /cc @RemcoSmitsDev we should be unblocked on having runner-dependant tasks now. Release notes: - N/A
2024-07-01 13:59:19 +00:00
"Rust": {
"tasks": {
"variables": {
"RUST_DEFAULT_PACKAGE_RUN": "zed"
}
}
Fix `Cargo.toml` formatting (#7886) This PR disables the formatting for `.toml` files within the Zed repo, as the formatter provided by the TOML language server messes things up. Release Notes: - N/A
2024-02-16 02:54:43 +00:00
}
WIP: Add a setting to visually redact enviroment variables (#7124) Release Notes: - Added bash syntax highlighting to `.env` files. - Added a `private_files` setting for configuring which files should be considered to contain environment variables or other sensitive information. - Added a `redact_private_values` setting to add or remove censor bars over variable values in files matching the `private_files` patterns. -(internal) added a new `redactions.scm` query to our language support, allowing different config file formats to indicate where environment variable values can be identified in the syntax tree, added this query to `bash`, `json`, `toml`, and `yaml` files. --------- Co-authored-by: Nathan <nathan@zed.dev>
2024-01-31 19:42:09 +00:00
},
ci: Move collab to Dockerfile-collab (#18515) This makes it possible to have multiple Dockerfiles, each with their own `.dockerignore`. Previously any docker builds would always include anything inside `.dockerignore`. I believe this feature may require `export DOCKER_BUILDKIT=1` but we use that in CI already.
2024-09-30 20:14:26 +00:00
"file_types": {
"Dockerfile": ["Dockerfile*[!dockerignore]"],
"Git Ignore": ["dockerignore"]
},
Add `hard_tabs: false` in project settings (#17357) # Problem I have a custom system-wide rustfmt configuration, and use tabs over spaces. So when I contribute to Zed, I will get lots of formatting errors. # Proposition - ~~Add rustfmt.toml (to specify that you are using the default rustfmt configuration, see https://github.com/rust-lang/cargo/issues/14442)~~ - Add `hard_tabs: false` to `.zed/settings.json` for people using tabs over spaces. Release Notes: - N/A --------- Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>
2024-09-04 16:30:28 +00:00
"hard_tabs": false,
Clean up whitespace (#10755) I saved the `file_types.json` file and got a diff because it had some trailing whitespace. I ran [`lineman`](https://github.com/JosephTLyons/lineman) on the codebase. I've done this before, but this time, I've added in the following settings to our `.zed` local settings, to make sure every future save respects our desire to have consistent whitespace formatting. ```json "remove_trailing_whitespace_on_save": true, "ensure_final_newline_on_save": true ``` Release Notes: - N/A
2024-04-23 17:31:21 +00:00
"formatter": "auto",
"remove_trailing_whitespace_on_save": true,
"ensure_final_newline_on_save": true
Ensure json uses a tab size of 4
2023-07-31 17:08:40 +00:00
}
Reference in a new issue Copy permalink