Zazzle integrated scrollToNode into Uize.Fx and it was suggested that we create a separate Uize.Fx.Scroll module in order to not unnecessarily weigh down Uize.Fx. The problem now is that Uize.Fx.Scroll still pulls in Uize.Fx even though it doesn't leverage any of the functionality, so we're also requiring all of Uize.Fx's depenencies.
Seems like what we really want is a Uize.Effects namespace (like Uize.Str) and then have a Uize.Effects.Styles module (for Uize.Fx) and then move Uize.Fx.Scroll to Uize.Effects.Scroll.
Thoughts?
Zazzle integrated
scrollToNodeintoUize.Fxand it was suggested that we create a separateUize.Fx.Scrollmodule in order to not unnecessarily weigh downUize.Fx. The problem now is thatUize.Fx.Scrollstill pulls inUize.Fxeven though it doesn't leverage any of the functionality, so we're also requiring all ofUize.Fx's depenencies.Seems like what we really want is a
Uize.Effectsnamespace (likeUize.Str) and then have aUize.Effects.Stylesmodule (forUize.Fx) and then moveUize.Fx.ScrolltoUize.Effects.Scroll.Thoughts?