Expose Blade formatter ignore ranges - #184
Merged
JohnathonKoster merged 2 commits intoAug 22, 2026
Merged
Conversation
Contributor
Author
|
Any thoughts on this or questions I can help with? |
Contributor
Nope! It's on my radar, and going to include it in the next release. Wrapping up a few things behind the scenes on my end before that 👀 |
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
2 participants
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.
Summary
This exposes a small
getBladeIgnoreRanges()API around the ignore ranges already collected by the Blade lexer.The returned values contain only
startandendsource offsets. Internal lexer resume state remains private, and the parser now shares the same collection helper so the public result follows the formatter's existing marker and syntax-plugin behavior.The API is intended for this draft Laravel Pint change, where Pint needs to protect ignored content from its own Blade pre- and post-formatters as well as from Prettier.
Testing