Whitespace error when rendering components - #1588
Closed
djanowski wants to merge 1 commit into
Closed
Conversation
Member
|
Hi, thanks for bringing this up, it's indeed not what you'd expect though not yet sure if it's intentional or not. I don't know where it's coming from yet, I hope it's posthtml-components and not the PostHTML parser/renderer itself. Would be great to get this fixed, yes 👍 |
Author
|
@cossssmin Thank you for your quick reply! Turns out the template that I was using (also the stub I added here) does have a newline at the end of the file, but most editors hide this, and it's hard to prevent it. It does seem like a posthtml-components issue, however I doubt that they'll want to trim component source when they read files :( |
Member
|
If you want to work on a PR to posthtml-components I'll be happy to review and get it merged :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If you confirm this is a bug, I'll try to find a fix.