Trim leading/trailing whitespace from fileHeaderComment
#138
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.
While testing 0.1 on some existing projects, I found a slight issue when using
fileHeaderComment
with multiline strings in yaml.Lets say that we define the following configuration:
You'd expect it to generate some code like this:
// Generated by Create API // https://github.com./CreateAPI/CreateAPI // // swiftformat:disable all import Foundation // ...
However it will actually include two lines between the comment and the import statement because Yaml seems to add a trailing whitespace after the multiline string.
To address this, I've updated the generator so that it trims whitespace and newlines from the generated output. I also added a dedicated test to validate the behaviour since there wasn't one before.