> > reproduces working JS APIs
This is the goal! Reproducing libraries in pure Elm is much safer and more desirable than writing wrappers around JS. Make sure that whatever you do, you respect Elm's philosophy: all data is immutable, and side-effects are always wrapped in a Task or a Cmd. On Sun, Jun 19, 2016 at 1:31 PM, Dan P <[email protected]> wrote: > I realize elm-date-extra <https://github.com/rluiten/elm-date-extra> exists, > but it's bloated, (apparently) unstable, reproduces working JS APIs, and is > not likely to be merged to core any time soon[1]. I'm considering making a > simplified fork of the former, but this rejected pull request > <https://github.com/elm-lang/core/pull/214> gives me pause. Can anyone > more familiar with the Elm ecosystem please advise? > > [1]: Not to say that it doesn't also provide useful functionality! But > core.Date is a little spartan, don't you think? > > > > On Sunday, June 19, 2016 at 3:03:51 PM UTC-4, Dan P wrote: >> >> (e.g. Date.setDate() in JS) >> >> Or would a pull request not be in vain? >> >> Compare: >> http://package.elm-lang.org/packages/elm-lang/core/4.0.1/Date >> >> >> https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Date >> >> -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
