For a better interface though is there a way you could just go over the list and see if there is an Html.class attribute in it and just append your new values to it (or prepend whichever)? That would get rid of the specialized types in the front-end while allowing you to mix and merge as you need in pre-processing?
Not really; this was raised repeatedly in the past <https://groups.google.com/forum/#!topic/elm-discuss/KHoBr1me8_4>, but as far as I know, nothing ever came of it. But Options has become a strength of elm-mdl, I think: It’s a uniform way to configure components. E.g.,: Button.render Mdl [0] model.mdl [ Button.fab , Button.ripple , Button.onClick MyClickMsg ] [ Icon.i "add"] Note lines 2—4. Also, earlier, elm-mdl allowed user to install arbitrary Html.Attributes along with Options, but users kept finding seemingly reasonable things to do with that which would inadvertently break the underlying component. -- 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.
