Fix parsing of tag descriptions with continuation lines starting with *

[tmdk]

When a tag description contains continuation lines that begin with *, the * appears twice in the parsed output. This affects block-style @param descriptions (common in WordPress docblocks) where list items or @type alignment uses a leading star:

/**
 * @param array $foo {
 *     Description of foo.
 *
 *     @type string $bar Description of bar with
 *                       * a list
 *                       * spanning *multiple* lines
 * }
 */

The parsed description for $foo would incorrectly contain ** a list instead of * a list.

Root cause

AbstractPHPStanFactory::tokenizeLine() worked around a PHPStan lexer limitation by splitting TOKEN_PHPDOC_EOL tokens that contained trailing whitespace into two tokens: a bare EOL and a separate TOKEN_HORIZONTAL_WS. This placed * in both token values. When PHPStan's parseText() stopped early at a tag-like token (e.g. @type) and rolled back, joinUntil() concatenated both raw token values, doubling the star.

Fix

Prefix every continuation line with "* " (star + space) before tokenizing. The PHPStan lexer's TOKEN_PHPDOC_EOL pattern matches exactly \n + optional whitespace + * (star + one space), so it always consumes the inserted "* " as part of the EOL token, leaving the original indentation as a separate subsequent token. A trim(..., "* \t") on every EOL token value then strips the inserted "* " back out, reducing each EOL to a plain "\n". The manual split into a separate TOKEN_HORIZONTAL_WS is no longer needed.

Changes

• src/DocBlock/Tags/Factory/AbstractPHPStanFactory.php — revised tokenizeLine()
• tests/integration/InterpretingDocBlocksTest.php — regression test covering the
  block-description case with embedded @type lines and star-prefixed continuation lines

[jaapio]

Please have a look at the code style.
I have a question about the implementation about how the implementation is done. But that's open for discussion.

[tmdk]

Please have a look at the code style. I have a question about the implementation about how the implementation is done. But that's open for discussion.

I was looking for commands to run linters in the wrong places and didn't notice the Makefile! Sorry about that

[jaapio]

Thanks a lot! When the pipeline passes I will merge this and create a new release