We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using VSC 1.23.1 and the latest version of this extension. My settings are:
"beautify.options": { "end_with_newline": true, "preserve_newlines": true, "selector_separator_newline": false },
When using a LESS mixin which has the ability to pass in nested rules as the mixin content such as:
.lg-up(@rules) { @media screen and (min-width: 900px) { @rules(); } }
What I would expect the code format to look like:
.lg-up( { background: #eaeaea; background-image: linear-gradient(to bottom, rgba(0, 0, 0, 0.1) 0%, rgba(0, 0, 0, 0) 60%); } );
What is actually happening:
Basically the final closing bracket gets returned onto the next line.
Is there anything I can do in the config to prevent this, or is this an issue with the extension?
Thanks!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm using VSC 1.23.1 and the latest version of this extension. My settings are:
When using a LESS mixin which has the ability to pass in nested rules as the mixin content such as:
What I would expect the code format to look like:
What is actually happening:
Basically the final closing bracket gets returned onto the next line.
Is there anything I can do in the config to prevent this, or is this an issue with the extension?
Thanks!
The text was updated successfully, but these errors were encountered: