Re: [elm-discuss] Catch Elm.Main.fullscreen "unexpected argument" error?

Alternatively, you could pass the data as Value in your program and use > multiple decoders to extract the data but that would be a little bit more > complicated. > > > > On Thu, Oct 13, 2016 at 10:31 PM, Kevin Berridge > wrote: > >> Is there a way to catch the &qu

[elm-discuss] Re: Catching error in fullscreen/App.programWithFlags

uld always have the program message back 'out' if it was successful, > though I'd go with changing how the data is passed in). > > On Saturday, October 15, 2016 at 11:20:11 AM UTC-6, Kevin Berridge wrote: >> >> I'm using App.programWithFlags to initiali

[elm-discuss] Catching error in fullscreen/App.programWithFlags

I'm using App.programWithFlags to initialize the state of my model from local storage (as described in this blog article ). But when the schema of my model changes (ex: I added a new field to a record ty

[elm-discuss] Catch Elm.Main.fullscreen "unexpected argument" error?

Is there a way to catch the "You are trying to initialize module `Main` with an unexpected argument." error when calling Elm.Main.fullscreen({}) with out of date arguments? I tried wrapping it in a try/catch, but the catch is not running. What I'm really trying to do is pass in state that was