Fix/928 autoformatting docs#1118
Open
aaroncymor wants to merge 4 commits intofeldroy:mainfrom
Open
Conversation
…wn files inside `docs` directory
…n code with Air tags.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Integrates
blacken-docsto auto-format Python code blocks in Markdown documentation while preserving intentional Air tag nesting patterns using<!-- blacken-docs:off/on -->guards.Fixes issue #928
Pattern
Follows the existing formatting workflow established in justfile.
Reviewer Focus
<!-- blacken-docs:off/on -->guards are only around Air tag code blocks with intentional multi-line nesting (e.g.,air.Html(),air.layouts.mvpcss()with nested children), not around plain Python code.--line-length 120matches project's Ruff configuration.Checklist