[] operator does not return usable ruleset values.
See original GitHub issueMap operator seems to not return anything reasonable if the value of interest is a ruleset.
Example:
@typography: {
@h1: {
font: roboto;
font-weight: 300;
font-size: 9.6rem;
line-height: 9.6rem;
text-transform: none;
}
}
#usage {
@x: @typography[@h1];
r: @x[font]; // err: could not evaluate variable call @x
@x(); // err: could not evaluate variable call @x
}
Expected:
@x
value should be a proper DR for both subsequent statements to work.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
CA1021: Avoid out parameters (code analysis) - .NET
Cause. A public or protected method in a public type has an out parameter. By default, this rule only looks at externally visible...
Read more >Rules in Distro - Chili Hub
A ruleset is a rule or group of rules that will be leveraged in order to determine assignment. In the past, rules were...
Read more >Rule Designer Messages - IBM
Rule Designer Messages - Messages pertaining to the rule engine ; GBRED0019E, The type ''{0}'' is not a valid condition type ; GBRED0020E,...
Read more >Business Rules Collection Data Types - Code Effects
The only operators that are not allowed with value typed collections are is and is not. This will look familiar to rule authors...
Read more >Rule operators and grouping symbols - Cloudflare Docs
Create and deploy rules and rulesets in different Cloudflare products ... Comparison operators return true when a value from an HTTP request ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It seems that this was fixed with other fixes. The latest version of Less (3.12.2) does not have this issue. The output is, as expected:
Closing as fixed.