New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: clean up template whitespace #145
chore: clean up template whitespace #145
Conversation
👋 @,
Thank you, 🤖 Clarity Release Bot |
Is this a change to the linter or prettier config? I don't see a config file change |
No. I just cleaned up the odd whitespace formatting |
Right, so manually fixing things is not going to be a longer term fix. If prettier is doing this - we need to fix the prettier config so it doesn't happen again. The next time someone edits one of these files and hits save, prettier will mangle it again. |
Prettier won't mangle these changes. |
Prettier preserves existing whitespace which 1) mangles tags when adding newlines and 2) keeps unnecessary whitespace when removing newlines. The commits in this PR change insignificant whitespace and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please backport to supported version branches too, or we may have troubles cherrypicking and merging future backports in these files.
This odd formatting was likely introduced by `prettier`.
This odd formatting was likely introduced by `prettier`.
This odd formatting was likely introduced by `prettier`.
This is backported in #161. |
🎉 This PR is included in version 13.4.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information