Dominik Moritz
Dominik Moritz
I'll do this in the next major version.
I think we should do this in webpack somehow or with lazy imports (maybe later).
Yes, in production only, though (or have a somehow the npm version as default so VL and VG devs can use the editor)!
Can you elaborate? `performance.now()` is more accurate, no?
Is that actually an issue for benchmarking? I'd like to see an example that's problematic before dismissing it.
Adding stack doesn't hurt in this case, though, right? I guess we can make an exception when the color field is the same as the categorical field.
I don't understand the rule. Also note that you usually want to use > instead of != To break symmetries.
EX and EY are just encodings and you never say that they are the x or y encoding, though.
This should be the same as this, right? ``` hard(no_stack_with_bar_area_discrete_color,E) :- mark(bar;area), channel(E,color), discrete(E), field(E,F), field(EE,F) not channel(EE,x), not channel(EE,y), not stack(_). ```
Can you provide some code to reproduce and screenshots that show the issue?