I have attached a simple example. I have a model with a field called 'currentQueryTips'.
A list is filtered using the current query string, coming through an input field. If you run the test you will see that the view is always one step behind the input. In a previous iteration, I had the query filter function in the view and everything worked well. As I said before though, I think I did this more elegantly a few months ago, trying to remember how... Any help is appreciated! On Thu, 10 Nov 2016 at 16:51 OvermindDL1 <overmind...@gmail.com> wrote: > Not something I've ever experienced and of which should be fairly > impossible. > > Do you have a simple reproduceable test-case that we can play with? > > > On Thursday, November 10, 2016 at 8:43:30 AM UTC-7, John Orford wrote: > > I have fallen into this trap a few times, > > 1) I update my model > > 2) The View doesn't change > > 3) Some other action occurs > > 4) My view changes with the first update > > My view is one step behind. > > I have fixed this before a few times (been a while ago). > > And rather than tinkering, I thought I would ask what the canonical > solution is. > > It's a simple mistake, but suspect common also, might help others. > > -- > 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 elm-discuss+unsubscr...@googlegroups.com. > 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Test.elm
Description: Binary data
