-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
htmlWhitespaceSensitivity is not being taken into account #93
Comments
The plugin currently overrides this setting for a variety of reasons, and is a non-trivial thing to take into account at this time (#91 (comment)). The array directive item is a separate issue, not related to whitespace sensitivity that I'd look at separately (the Laravel Pint integration works correctly for this scenario, however). |
@luveqz I've released v2.1.2 to help prevent the issue that wrecked your array input. If you're curious, it was caused by an internal workaround that prevents items like the following from being shoved to a single-line by prettier: @props([
'value',
'value',
'value',
'value',
'value',
]) This internal workaround was a bit too aggressive with what it was doing so I added a few checks to stop it from going into this logic. Re. the |
@JohnathonKoster ❤️ and if you would like some additional eyes or help, I would be happy to chip in. We have a number of templates that are mostly HTML w/ just a little Blade sprinkled here and there, so support for |
Just an update that this is currently slated for the next major release of the plugin. Hopefully within the next few weeks 👍 |
Problem
Even when I set the htmlWhitespaceSensitivity rule to
strict
, the plugin keeps turning this:into this:
Or even this:
into this:
Demo
Open this minimal StackBlitz demo and run:
The text was updated successfully, but these errors were encountered: