formatter
Here are 1,234 public repositories matching this topic...
-
Updated
Mar 12, 2022 - Python
Discussed in mvdan/sh#838
Originally posted by antichris April 3, 2022
Is there a specific design reason why the space preceding a comment is removed when it follows an open parenthesis, or is it by accident?
Given the input
#!/bin/sh
foo() { ## (bar, [baz])
:
} ## qux
corge() ( ## (graGood evening!
This is a feature request (AFAIKT there's no configuration option or duplicate issue for this).
In many cases where nightly rustfmt is applied by CI in public repositories, users will often run cargo fmt themselves directly or through their editor causing warnings arising from using the stable rustfmt where the nightly is required. E.g.:
$ cargo fmt
Warning
-
Updated
Apr 5, 2022 - TypeScript
-
Updated
Apr 5, 2022 - Python
-
Updated
Apr 5, 2022 - TypeScript
-
Updated
Apr 5, 2022 - JavaScript
-
Updated
Apr 5, 2022 - Ruby
-
Updated
Apr 4, 2022 - Java
-
Updated
Nov 7, 2021 - Vim script
-
Updated
Nov 14, 2021 - Swift
GDPR compliance
-
Updated
Apr 5, 2022 - PHP
-
Updated
Mar 30, 2022 - C#
-
Updated
Mar 23, 2022 - Haskell
-
Updated
Jan 26, 2022 - TypeScript
Update README.md
We need to update our README.md file before the 1.0 release.
-
Updated
Apr 6, 2022 - Rust
-
Updated
Mar 31, 2022 - JavaScript
-
Updated
Mar 22, 2022 - JavaScript
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."
Suspect regression. Using v 4.0.1 (Gentoo X86_64). Having just installed black (v22.1.0), reformatting produced multiple W503 messages. Attempted to utilize extended-ignore and reloaded/rescanned project. Warnings persisted. I ensured no W503/W504 ignores were present in code or configuration. Only after adding explicitly W503 to extended-ignore would flake8 be satisfied.
_Originally posted by