Fix docblock parser to handle multiline descriptions for all tags #602
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.
The docblock parser was truncating multiline descriptions when the first line didn't end with
{. This affected@paramdescriptions inUtils\http_request()(e.g., the$dataparameter lost its continuation line "or in the body for POST requests.") and would similarly affect@return,@throws, and other docblock tags.Root cause: Parser only tracked multiline descriptions when they ended with
{, ignoring other line-ending characters like commas.Changes:
$in_paramfor all docblock tags (@param,@return,@throws, etc.), not just those ending with{@tag instead of checking for}Testing:
Verified that multiline descriptions work correctly for:
@paramtags (original issue)@returntags@throwstagsOriginal prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.