I had a similar problem with a field named `default`. I think you have to avoid all Javascript reserved words for records passed through ports. http://www.w3schools.com/js/js_reserved.asp
It is an unfortunate leak of Javascript constraints into the Elm world. It does seem that the compiler could warn about such cases as it knows exactly which types of values are going over ports. On Wednesday, October 19, 2016 at 4:48:42 PM UTC-5, Craig Bilner wrote: > > I'm probably missing something obvious here but when my port is a record > with an attribute of `class` it comes through as `undefined`. Is there some > documentation somewhere outlining reserved words in this area? Should the > compiler throw? > > -- 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.
