Fix {@ escaping in markdown to preserve PHPDoc annotations like {@inheritDoc} #753
Conversation
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
nicodevs
force-pushed
the
nd/fix-escaping-in-markdown-to-preserve-phpdoc-annotations-like-inheritdoc
branch
from
fa78b77 to
f78a1f2
Compare
............................................................................ ...................................✓...... ──────────────────────────────────────────────────────────────────── Laravel FIXED ................................... 118 files, 1 style issue fixed ✓ src/Console/BuildCommand.php not_operator_with_successor_space, no_whites… )
damiani
approved these changes
Nov 21, 2025
damiani
deleted the
nd/fix-escaping-in-markdown-to-preserve-phpdoc-annotations-like-inheritdoc
branch
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.
Fixes #749 - PHPDoc
{@inheritDoc}annotations in markdown code blocks were being corrupted.Given the following Markdown:
The
@escaping ('@' => "{{'@'}}") was turning{@inheritDoc}into{{{'@'}}inheritDoc}- three opening braces, which is invalid Blade syntax. The build failed with aParseError: syntax error, unexpected token "{".The fix: Add
'{@' => '{@'to the replacement array. Sincestrtrprioritizes longer matches first,{@is matched before@, preserving the original sequence.Added test case for
{@inheritDoc}in code blocks.