Marek, about the tea-component package: If you're discouraged by the boilerplate for nested update and view functions, you can clean-up the boilerplate with a single function each... no need to create an entire abstraction package.
On Wednesday, April 19, 2017 at 3:34:31 PM UTC-4, Marek Fajkus wrote: > > Marek, >> >> One difference might be that we don't deal with sign-in in SPA itself. >>> We're using Html.programWithFlags and passing user info to elm on >>> embedding. >> >> >> Good stuff. Less work when you don't have to worry about auth states. >> > > it's helping us a lot. Anyway this architecture is used even in js app and > predates me joining project. Whole login happens on different domain with > different service. Anyway it also means we have to do one XHR request > before starting app. > > this is example of idea I'm experimenting with: > https://github.com/turboMaCk/elm-app-composition-example > that led to: https://github.com/turboMaCk/tea-component > > we're not using exactly that right now. Also package itself is removed > from package.elm-lang.org. It will be republished once I manage to change > name + docs and I don't really enjoy doing that so I'm taking my time:D > -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
