Fix options being dropped when a parameter description is multi-line

[enricodelazzari]

Problem

When an OpenAPI parameter has a multi-line description (free-form Markdown, which is perfectly valid per the spec), the generated command throws at runtime as soon as it's executed:

The "order" option does not exist.

Root cause

EndpointCommand::buildSignature() interpolates the raw description into Laravel's signature DSL:

$parts[] = "{--{$optionName}= : {$description}}";

Laravel's signature parser extracts tokens with preg_match_all('/\{\s*(.*?)\s*\}/', ...) — no s modifier, so . doesn't match newlines. A {--order= : line1\n\nline2} block is therefore never matched, and the option is silently dropped (it doesn't even show up in --help).

But buildSignature() still records the parameter in $queryParamOptionMap / $pathParamOptionMap. At runtime buildRequestUrl() iterates that map and calls $this->option($name) on the option that was never registered → InvalidOptionException.

This breaks every endpoint whose parameters have multi-line descriptions ({/} in a description hit the same problem).

Minimal reproduction

[$name, $args, $opts] = Illuminate\Console\Parser::parse("cmd {--order= : One line}");
// → option --order registered

[$name, $args, $opts] = Illuminate\Console\Parser::parse("cmd {--order= : One line.\n\nTwo lines.}");
// → NO options registered

Fix

Sanitize the description before embedding it in the signature: collapse whitespace runs (including newlines) into single spaces and strip {/}.

Tests

Added a regression test in QueryParametersTest that registers a query parameter with a multi-line description and asserts the command runs and sends the parameter. It fails on main with the exact The "--order" option does not exist. error and passes with the fix.

Full suite (348 tests) green; Pint passes. (The 2 pre-existing PHPStan errors at EndpointCommand.php:49 are unrelated to this change.)

🤖 Generated with Claude Code