I always used "lazy" for not updating value in rendered input after every key press. It is equivalent of react's "shouldComponentUpdate".
śr., 21 gru 2016 o 12:28 użytkownik Simon <[email protected]> napisał: > Yes, I have the same type of issue, but with the data attached to Blur > messages attached arbitrarily to messages in new views. The way I solved it > so far was to use Html.Keyed on the form page. > > Simon > > On Tuesday, 20 December 2016 22:33:26 UTC+1, Duane Johnson wrote: > > > On Tue, Dec 20, 2016 at 2:03 PM, Wouter In t Velt <[email protected]> > wrote: > > > - Is there a better way to *prevent* this from happening (rather than > relying on our predictive instincts and applying Keyed when we suspect a > leak)? > > > I like that you're asking this question, because for me it sits at the > core of what I find attractive about Elm: the language gives us a break > from worrying about all of the ways things might break, and lets us focus > on the business logic of an app. > > -- > 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. > -- 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.
