[11.x] Support New Lines in Command Argument and Option Descriptions #54057
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.
This PR introduces support for new lines in argument and option descriptions within the
{}
template in theparse()
method. Previously, new lines were escaped, but this change allows for easier formatting of long descriptions, which improves readability.The main benefit of this change is improved readability, making it easier to break up long descriptions without affecting the current functionality.
A test has been added to ensure the
parse()
method correctly handles new lines in descriptions. The test verifies that everything works as expected without introducing any regressions.In summary, this PR makes command signature descriptions more readable and ensures the code is safer without causing any breakage.