You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: None of this is going to happen any time soon. The last breaking change we made was forced by a new version of Elm. But it is a good idea to keep a wish list of things to change in the future.
sequential scale can easily support axes, but don't at the moment
Loosen type signature of invertExtent to support threshold scales.
Use partial application for scales to simplify type signatures.
Switch from record to list style for band/point configs.
Change architecture of Force to allow for nicer custom forces as well as better dead code elimination
Transition module needs some work. Easing is an opaque type for some reason, this doesn't make much sense, since it's an Interpolator under the hood. So is Transition, again this goes against most of the other design of elm-visualization. We also have nice stagger primitives in Interpolation, but can't really apply them easily, since we don't get easing that way...
Consider renaming Interpolation to Interpolate (i.e. Interpolate.float reads much nicer)
Note: None of this is going to happen any time soon. The last breaking change we made was forced by a new version of Elm. But it is a good idea to keep a wish list of things to change in the future.
invertExtent
to support threshold scales.Shape.stack
can be made more intuitive.Easing
is an opaque type for some reason, this doesn't make much sense, since it's anInterpolator
under the hood. So isTransition
, again this goes against most of the other design of elm-visualization. We also have nice stagger primitives in Interpolation, but can't really apply them easily, since we don't get easing that way...Interpolate.float
reads much nicer)See also #10.
The text was updated successfully, but these errors were encountered: