Fix Parsing of Multiline Argument Descriptions #527
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: #477
This pull request addresses a parsing error in the WP CLI handbook where multiline argument descriptions in the
Utils\http_request()
method were not being handled correctly. Previously, the parser failed to recognize,
as a valid character that could indicate the continuation of an argument description onto a new line.Changes Made:
Updated the conditional check in the parsing logic. Now, the parser recognizes both
{
and,
characters as potential indicators of a multiline argument. This ensures that argument descriptions that continue after these characters are correctly parsed and included in the documentation.