Like Peter, I think the key issue is how to build a large app with 1000 line files.
On authentication, this might help: http://simonh1000.github.io/2016/05/phoenix-elm-json-web-tokens/ On Tuesday, 2 May 2017 16:10:03 UTC+2, Alan McCann wrote: > > I echo Peter Damoc's entry + authentication (e.g. JWT) > > On Monday, April 24, 2017 at 10:06:53 AM UTC-4, Jeff Schomay wrote: >> >> Hello, >> >> I am considering doing some training material on working with Elm in >> production. I want to focus on areas that people struggle with after they >> are already familiar with Elm. What concepts continue to confuse you? >> What product requirements have been difficult to achieve with Elm? What >> is most painful about your Elm codebase? >> >> Some topics I have already thought of: >> >> - decoders >> - debouncing (http autocomplete input field for example) >> - scroll to element >> - testing >> - unwieldy update functions >> - api design >> >> If you have anything you'd like me to consider, please add it to the >> list. Thank you! >> > -- 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.
