rust/comprehensive-rust
1
0
Fork 0
mirror of https://github.com/google/comprehensive-rust.git synced 2024-11-24 17:06:37 +02:00
Code Issues Releases Activity
6148caed7a
comprehensive-rust/dprint.json

31 lines
785 B
JSON
Raw Normal View History

Format files with `dprint` (#711) The dprint formatter is a flexible system which will use sandboxed WebAssembly formatters to format our code (mostly: it calls out to `rustfmt` for Rust code). A particularly interesting feature is that dprint can format Rust code blocks in the Markdown files. However, before we turn that on, we need to have a way to normalize the Markdown text as it is extracted[1]. That is so that the word put into the translations is kept after the reformatting. [1]: https://github.com/google/mdbook-i18n-helpers/issues/19
2023-05-30 17:04:19 +02:00
{
"lineWidth": 80,
"json": {},
"markdown": {
"textWrap": "always"
},
"exec": {
Update `exec` plugin to latest version (#1046) The latest version of `dprint` doesn't work with our old version of the `exec` plugin. This fixes the config based on https://github.com/dprint/dprint/issues/726.
2023-08-02 11:30:43 +02:00
"commands": [{
Format Python files with YAPF (#1360)
2023-10-18 19:56:05 +02:00
"command": "yapf3",
"exts": ["py"]
}, {
Use stable rustfmt (#2168) This uses the `rustfmt` from the stable toolchain, instead of nightly. At the moment, nightly's `rustfmt` is nonfunctional, but in general we don't need bleeding-edge formatting (and in fact, the more often formatting changes, the more often we'll get spurious failures on PRs, as we are today). Fixes #2165.
2024-06-25 10:07:15 +02:00
"command": "rustup run stable rustfmt --edition 2021",
Update `exec` plugin to latest version (#1046) The latest version of `dprint` doesn't work with our old version of the `exec` plugin. This fixes the config based on https://github.com/dprint/dprint/issues/726.
2023-08-02 11:30:43 +02:00
"exts": ["rs"]
}]
Format files with `dprint` (#711) The dprint formatter is a flexible system which will use sandboxed WebAssembly formatters to format our code (mostly: it calls out to `rustfmt` for Rust code). A particularly interesting feature is that dprint can format Rust code blocks in the Markdown files. However, before we turn that on, we need to have a way to normalize the Markdown text as it is extracted[1]. That is so that the word put into the translations is kept after the reformatting. [1]: https://github.com/google/mdbook-i18n-helpers/issues/19
2023-05-30 17:04:19 +02:00
},
"excludes": [
Exclude `book/` directory from auto-formatting (#852) The directory contains generated files and should be ignored when reformatting.
2023-06-22 16:13:53 +02:00
"/book/",
Automatically format YAML, CSS, and JS files (#1272) Initially, I also formatted the templates in `theme/`, but this triggers https://github.com/prettier/prettier/issues/11834. So I exclude them for now. --------- Co-authored-by: Ming-Ying Chung <mych@chromium.org>
2023-10-02 07:48:00 +02:00
"/theme/*.hbs",
Test translations using same source as for publish (#1492) Before we would run `mdbook test` using the current Markdown sources. This is subtly wrong: we publish the course using back-dated sources, so we should therefore also run the tests using the same sources (this ensures that the code snippets actually work). After this commit, all translatable content lives in exactly two directories: - `src/` - `third_party/` We need to restore both directories when testing and when publishing. This ensures consistency in the Markdown text and in the included source code. A new `.github/workflows/build.sh` script takes care of preparing the two directories according to the date in the PO file (if any). To ensure we can restore all of `third_party/` to an old commit, the non-changing `third_party/mdbook/book.js` file has been moved to `theme/book.js`. The file is generated by `mdbook init --theme`, making it suitable for modification by the user (us). Symlinks have been added to `third_party/mdbook/` to indicate that the files ultimately came from upstream.
2024-01-04 18:04:44 +02:00
"/theme/book.js",
Format files with `dprint` (#711) The dprint formatter is a flexible system which will use sandboxed WebAssembly formatters to format our code (mostly: it calls out to `rustfmt` for Rust code). A particularly interesting feature is that dprint can format Rust code blocks in the Markdown files. However, before we turn that on, we need to have a way to normalize the Markdown text as it is extracted[1]. That is so that the word put into the translations is kept after the reformatting. [1]: https://github.com/google/mdbook-i18n-helpers/issues/19
2023-05-30 17:04:19 +02:00
"/third_party/",
"target/"
],
"plugins": [
Update `exec` plugin to latest version (#1046) The latest version of `dprint` doesn't work with our old version of the `exec` plugin. This fixes the config based on https://github.com/dprint/dprint/issues/726.
2023-08-02 11:30:43 +02:00
"https://plugins.dprint.dev/exec-0.4.3.json@42343548b8022c99b1d750be6b894fe6b6c7ee25f72ae9f9082226dd2e515072",
Run dprint config update (#1273) This updates the plugins to the latest version.
2023-09-28 22:52:00 +02:00
"https://plugins.dprint.dev/json-0.17.4.wasm",
Update `dprint` config (#1354) The new version of the Markdown plugin has the fix for https://github.com/dprint/dprint-plugin-markdown/issues/87. Fixes #1308.
2023-10-12 21:30:49 +02:00
"https://plugins.dprint.dev/markdown-0.16.2.wasm",
Automatically format YAML, CSS, and JS files (#1272) Initially, I also formatted the templates in `theme/`, but this triggers https://github.com/prettier/prettier/issues/11834. So I exclude them for now. --------- Co-authored-by: Ming-Ying Chung <mych@chromium.org>
2023-10-02 07:48:00 +02:00
"https://plugins.dprint.dev/toml-0.5.4.wasm",
"https://plugins.dprint.dev/prettier-0.27.0.json@3557a62b4507c55a47d8cde0683195b14d13c41dda66d0f0b0e111aed107e2fe"
Format files with `dprint` (#711) The dprint formatter is a flexible system which will use sandboxed WebAssembly formatters to format our code (mostly: it calls out to `rustfmt` for Rust code). A particularly interesting feature is that dprint can format Rust code blocks in the Markdown files. However, before we turn that on, we need to have a way to normalize the Markdown text as it is extracted[1]. That is so that the word put into the translations is kept after the reformatting. [1]: https://github.com/google/mdbook-i18n-helpers/issues/19
2023-05-30 17:04:19 +02:00
]
}
Reference in New Issue Copy Permalink