@less/test-data 4.9.0 → 5.0.0-alpha.2

package/tests-unit/lookup-interpolation/lookup-interpolation.less

@@ -1,127 +0,0 @@
-// `[...]` lookups inside `@{...}` interpolation, backported from Less 5.x.
-//
-// Before the backport the parser accepted only `@{name}`, so every form below
-// either failed to parse or — in string and url positions — silently emitted the
-// interpolation verbatim into the output. The url/quoted cases in particular are
-// regression coverage for that silent pass-through: a wrong-output bug that
-// produced no error and no warning.
-//
-// The bare `@map[key]` spelling is covered by at-rule-variable-deprecated.less,
-// where it is deprecated in structural positions.
-
-@sizes: {
-  tablet: 768px;
-  name: card;
-  @name: indirect-hit;
-  last-entry: tail;
-};
-
-@theme: {
-  color: blue;
-  @nested: {
-    name: inner;
-    label: "deep";
-    last-entry: nested-tail;
-  }
-};
-
-@paths: {
-  img: "/assets/img";
-};
-
-@which: name;
-
-// --- quoted strings ---
-.quoted {
-  single: "@{sizes[name]}";
-  chained: "@{theme[@nested][name]}";
-  quoted-value: "@{theme[@nested][label]}";
-  indirect-key: "@{sizes[@@which]}";
-  empty-key: "@{sizes[]}";
-  chained-empty-key: "@{theme[@nested][]}";
-  surrounded: "a-@{sizes[name]}-b";
-  twice: "@{sizes[name]}/@{theme[color]}";
-}
-
-// --- url() — the silent pass-through regression ---
-// An unquoted url() body was raw text in an Anonymous node, so neither the plain
-// nor the lookup interpolation resolved there while the quoted form did. Both
-// spellings are covered so the two cannot diverge again.
-@plain-path: "/plain";
-
-.url {
-  quoted: url("@{paths[img]}/hero.png");
-  unquoted: url(@{paths[img]}/plain.png);
-  unquoted-plain: url(@{plain-path}/no-lookup.png);
-  untouched: url(/static/literal.png);
-  untouched-quoted: url("/static/literal.png");
-  data-uri: url(data:image/svg+xml;base64,AAAA);
-}
-
-// --- ${...} property interpolation ---
-// Properties have no lookup grammar: `$name[key]` is a property reference followed
-// by literal `[key]`, and `prop: { … }` is a parse error in every scope, so nothing
-// can hold a ruleset to look into. `${...}` therefore stays narrow while `@{...}`
-// carries lookups, and the plain form must keep working unchanged.
-.property-interpolation {
-  color: red;
-  from-property: "${color}";
-  surrounded: "a-${color}-b";
-  bare: $color;
-}
-
-// --- selector interpolation ---
-.@{sizes[name]} {
-  a: b;
-}
-
-.@{theme[@nested][name]} {
-  c: d;
-}
-
-// --- property name interpolation ---
-.property {
-  @{sizes[name]}: from-lookup;
-  @{theme[@nested][name]}: from-chained-lookup;
-}
-
-// --- at-rule name and prelude ---
-@keyframes @{sizes[name]} {
-  from { opacity: 0; }
-  to { opacity: 1; }
-}
-
-@queries: {
-  tablet: ~"(min-width: 768px)";
-};
-
-@media @{queries[tablet]} {
-  .responsive {
-    e: f;
-  }
-}
-
-// --- custom property values ---
-.custom-property {
-  --from-lookup: @{paths[img]};
-  --from-chained: @{theme[@nested][name]};
-}
-
-// --- interpolation still resolves to a fixpoint ---
-// The inner `@{...}` arrives from a variable's value at eval time, so it is not
-// present in the source text of the outer reference.
-@inner: card;
-@outer: ~"@{inner}";
-
-.recursive {
-  g: "@{outer}";
-}
-
-// --- plain interpolation is unaffected by the lookup support ---
-.plain {
-  h: "@{which}";
-}
-
-.@{which} {
-  i: j;
-}

package/tests-unit/media-nested-type/media-nested-type.css

@@ -1,40 +0,0 @@
-@media screen and (max-width: 500px) {
-  .a {
-    color: red;
-  }
-}
-@media only screen and (min-width: 100px) {
-  .b {
-    color: blue;
-  }
-}
-@media all and (max-width: 9px) {
-  .c {
-    color: green;
-  }
-}
-@media print and (color) and (min-width: 1px) {
-  .d {
-    color: black;
-  }
-}
-@media screen and (max-width: 500px) {
-  .e {
-    color: red;
-  }
-}
-@media (max-width: 500px) and (min-width: 100px) {
-  .f {
-    color: red;
-  }
-}
-@media tester and (max-width: 500px) {
-  .g {
-    color: red;
-  }
-}
-@media screen and (max-width: 500px) {
-  .h {
-    color: red;
-  }
-}

package/tests-unit/media-nested-type/media-nested-type.less

@@ -1,51 +0,0 @@
-// A media type nested inside conditions must lead the flattened query,
-// otherwise the result is invalid CSS (issue #3694, #3764).
-@media (max-width: 500px) {
-  @media screen {
-    .a { color: red; }
-  }
-}
-@media (min-width: 100px) {
-  @media only screen {
-    .b { color: blue; }
-  }
-}
-@media (max-width: 9px) {
-  @media all {
-    .c { color: green; }
-  }
-}
-@media (min-width: 1px) {
-  @media print and (color) {
-    .d { color: black; }
-  }
-}
-
-// Already-correct ordering is preserved.
-@media screen {
-  @media (max-width: 500px) {
-    .e { color: red; }
-  }
-}
-
-// Queries without a media type are left untouched.
-@media (max-width: 500px) {
-  @media (min-width: 100px) {
-    .f { color: red; }
-  }
-}
-
-// Unknown media types are valid CSS non-matches, so they reorder too.
-@media (max-width: 500px) {
-  @media tester {
-    .g { color: red; }
-  }
-}
-
-// An escaped-string feature condition (Anonymous) must not be mistaken for a media type.
-@fc: ~"(max-width: 500px)";
-@media @fc {
-  @media screen {
-    .h { color: red; }
-  }
-}