Prevent introduction of trailing whitespace after headings with JavaScript formatter #35
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.
🤔 What's changed?
With the gherkin-utils JavaScript formatter, headings will have a trailing space introduced after them. When they have a title, this is not an issue, as the space is suffixed by the title itself i.e.
<heading>: <title>
. However, in the absence of a title - such as the typical use case of not including a title forExamples:
, the formatter introduces a trailing space at the end of the headings.This change ensures the space is included only when there is a title.
⚡️ What's your motivation?
Prevents the introduction of unexpected artifacts into gherkin tests that use the formatter - the trailing whitespace; and fixes #34.
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
To confirm the null check is required.
📋 Checklist: