Re: [elm-discuss] Re: Update Delay

Simplifying is a wonderful way to bug-hunt, one of my go-to methods. :-) On Sunday, November 13, 2016 at 2:28:00 PM UTC-7, John Orford wrote: > > My mistake! I was querying the previous list of strings rather than the > updated one. Good exercise though, simplifying helped me find the bug > On

Re: [elm-discuss] Re: Update Delay

My mistake! I was querying the previous list of strings rather than the updated one. Good exercise though, simplifying helped me find the bug On Sun, 13 Nov 2016 at 19:48, John Orford wrote: > I have attached a simple example. > > I have a model with a field called

Re: [elm-discuss] Re: Update Delay

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

[elm-discuss] Re: Update Delay

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)