pass --check option to black about blacken-docs HOT 7 CLOSED

no, sorry -- for the same reasons as #3

it's not simply passing through the option as we don't even access the part of black that does checking -- it would be implementing it and supporting it here which I am not interested in doing

thanks for the issue anyway!

from blacken-docs.

Could you please reconsider? Unfortunately, we can't depend on pre-commit tool.

You are right that it's not enough to pass --check to black. However, the implementation was almost trivial. I've implemented it before seeing your message: PR #43

from blacken-docs.

no, I don't want to support that feature

from blacken-docs.

note that you can already use the exit code (this tool returns nonzero when making changes)

from blacken-docs.

Ok, no problem!

Thank you for info about the exit code. However, I don't want blacken-docs to change files under me in this case.

By the way, I've found a work-around for non-destructive format checking:

./markdowncode README.md | black --check --diff -

markdowncode is a small script that extracts all Python code blocks:

#!/usr/bin/env python3
"""Extract Python code blocks from markdown file"""

import re
import sys
from textwrap import indent

doc = open(sys.argv[1])
blocks = re.findall(r"\n```python\n(.*?)\n```", doc.read(), re.DOTALL)
print(
    "\n\n\n".join(
        f'def test_{i}():\n{indent(block, " " * 4)}' for i, block in enumerate(blocks)
    )
)

from blacken-docs.

cool, thanks for sharing

from blacken-docs.

@shamrin not a place for advertising

from blacken-docs.