codeformatter

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

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.

Hey guys, I was trying to clean up some code and came upon this super niche edge case.

Here is the minimal reproducible example. Removing one or both ifs, removing the bottom comment or replacing the ruleorder with anything else does not result in the error.

# when using nested if-statements with___
if True:
    if True:
        ruleorder: ___a_ruleorder_and___

    # __

The error:

Error: ENOENT: no such file or directory, open 'C:\Git_work\Roku-Sample-App\source\*.brs'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.readFileSync (fs.js:551:33)
    at processFile (C:\Users\eg874k\AppData\Roaming\npm\node_modules\@willowtreeapps\wist\src\js\cli-engine.js:64:21)
    at executeOnFile (C:\Users\eg874k\AppData\Roaming\npm\node_modules\@willowtreeapp