You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I choose an element, like transition for example - and select the hint, "Add Missing Vendor Specifics" - it does it - but then re-formats the entire document.
Specifically, it puts extra lines between each LESS declaration. I spend enough time making my layout readable to me - without a chunk of code that's supposed to do one thing - impose its idea of a layout across the entire document. If I wanted to keep that hint action, I have to walk through and re-format to the way I like it.
I'd prefer if WE just did the micro-task at hand- and no more than that micro-task.
The text was updated successfully, but these errors were encountered:
You shouldn't be hand-inserting vendor specifics if you're writing Less. You should be using the autoprefixer post-processor plugin for the Less compiler instead and automate it as part of your build step.
(Not sure if Web Essentials was ever extended to support registering plugins; I rolled my own build solution for Less files because the Web Essentials method of having compiled output be part of the project files under source control is asinine.)
If I choose an element, like
transition
for example - and select the hint, "Add Missing Vendor Specifics" - it does it - but then re-formats the entire document.Specifically, it puts extra lines between each LESS declaration. I spend enough time making my layout readable to me - without a chunk of code that's supposed to do one thing - impose its idea of a layout across the entire document. If I wanted to keep that hint action, I have to walk through and re-format to the way I like it.
I'd prefer if WE just did the micro-task at hand- and no more than that micro-task.
The text was updated successfully, but these errors were encountered: