-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Transform #1761
Comments
Users should simply derive a new data field and use the new field. That said, I see that this would be painful:
Instead of making this specific to legend, I propose that we add a
|
A syntax that might be more appropriate for the new transform array might be:
|
Yes. Close this then? |
? Having reuseable code for this task doesn't mean we support this task by any mean. |
Oh, I meant close this issue and don't support replace. |
Why? The current way to do replace is still super annoying. (Write ugly chains of ternary operator) |
Never mind. I misunderstood that this issue has some other benefits besides sorting domains. |
Yes it does ;) |
Cool. Somebody implement this then :-P |
I wonder if it would be best implemented as a function in Vega expression though so it will benefit the whole stack. |
I defer that question to @jheer |
Actually something like |
We use this in #4020 😛 |
It might be worth documenting this somewhere. |
I'm at a loss as to how this was actually fixed / how this can be expressed ... is @kanitw's sat/sun/weekend example how this can be expressed now? |
Yes, you can write a calculate transform with an expression as in @kanitw's comment. |
I want to be able to specify what text is shown in the legend for ordinal colors but setting the domain and range only let's me override the colors but not the labels.
See vega/altair#278
The text was updated successfully, but these errors were encountered: