The docblock parser was truncating multiline descriptions when the first line didn't end with {. This affected @param descriptions in Utils\http_request() (e.g., the $data parameter 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:

• Set $in_param for all docblock tags (@param, @return, @throws, etc.), not just those ending with {
• Continue appending lines until encountering another @ tag instead of checking for }
• Add empty string guards before array access

// Before: Only tracked params ending with '{'
if ( ! empty( $ret['parameters'][ $param_name ][ $key ][2] )
    && '{' === substr( $ret['parameters'][ $param_name ][ $key ][2], -1 ) ) {
    $in_param = [ $param_name, $key ];
}

// After: Track all tags, terminate on next @ tag
if ( ! empty( $ret['parameters'][ $param_name ][ $key ][2] ) ) {
    $in_param = [ $param_name, $key ];
} else {
    $in_param = false;
}

Testing:
Verified that multiline descriptions work correctly for:

• @param tags (original issue)
• @return tags
• @throws tags
• Multiple multiline tags in the same docblock

• Fixes Parsing issue with multiline argument description #477

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.