Allow passing a value with spaces without wrapping it as an escaped string

[demoive]

With any value that has spaces in it (e.g. 1px solid red), fails to generate a proper CSS definition since LESS treats the argument as an array of values. You can get around this in your solution by passing it in as an escaped string (e.g. ~"1px solid red"). Out of your test cases, the following seem to contain this bug:

.test-compound
.test-function-param-preserve-second
.test-function-param-preserve-first
.test-function-param-preserve-double
.test-nested-coumpoun

Here is an example of the failing output:

.property(transition, all .5s ease, "webkit moz o");

.test-compound {
  -test-should: generate a property definition that looks correct;
  -less-property: ;
  -webkit-transition: [all, 0.5s, ease];
  -moz-transition: [all, 0.5s, ease];
  -o-transition: [all, 0.5s, ease];
  transition: [all, 0.5s, ease];
}

In my solution, I encountered this same problem, but resolved it by escaping the argument before using it. In your mixin, if you escape both the @property and @value arguments into new variables, I think it would be more robust. For example:

.property(@property, @value, @prefixes: '', @base: true) {
  @prop: e('@{property}');
  @vals: e('{@value}');

  // ...
}

[borodean]

Thanks for your input, @demoive!

(Too bad it took me 7 years to get back to it 😅)

[demoive]

Wow, indeed! You're welcome and have a good life! :-D

…

On Tue, 11 Feb 2020 at 21:01, Vadym Borodin ***@***.***> wrote: Thanks for your input, @demoive <https://github.com/demoive>! (Too bad it took me 7 years to get back to it 😅) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AADTJYEWJ5GU5FHCXFMV42TRCL7YBA5CNFSM4AFPAD4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELN3JEA#issuecomment-584823952>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADTJYBGCJNVI3JDEFUQ66DRCL7YBANCNFSM4AFPAD4A> .