formatter
Here are 1,282 public repositories matching this topic...
-
Updated
May 27, 2022 - Python
The motivation for this new option is outlined in #5345, and the option proposed here is a potential solution to that scenario.
Specifically, we need to introduce a new config option named something like doc_comment_code_block_width (but feel free to come up with a better name) that's used to set the width threshold used when rustfmt is reformating code blocks residing within doc comments.
-
Updated
Jun 7, 2022 - TypeScript
-
Updated
Apr 20, 2022 - Python
-
Updated
Jun 7, 2022 - TypeScript
-
Updated
Jun 7, 2022 - JavaScript
-
Updated
Jun 6, 2022 - Java
-
Updated
Apr 19, 2022 - Ruby
-
Updated
Jun 7, 2022 - Vim script
-
Updated
Nov 14, 2021 - Swift
GDPR compliance
-
Updated
Jun 7, 2022 - PHP
-
Updated
May 31, 2022 - C#
-
Updated
Jun 4, 2022 - Rust
-
Updated
May 23, 2022 - Haskell
-
Updated
Jun 7, 2022 - JavaScript
-
Updated
Jan 26, 2022 - TypeScript
Update README.md
We need to update our README.md file before the 1.0 release.
-
Updated
Jun 6, 2022 - TypeScript
Improve this page
Add a description, image, and links to the formatter topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the formatter topic, visit your repo's landing page and select "manage topics."
Perhaps we should document this issue in the FAQ? Using pre-commit with Black is pretty common (and it's not always instantly clear it passes all of the files to the hook directly bypassing any file discovery the hook may implement). I'd suggest pre-commit's exclude configurations first, and then black's force-exclude.
_Originally posted by @ichard26 in psf/black#3013