[savage13]

When searching for objects, the debounce() function can call multiple instances of search() and these collide if the network activity persists for too long.

• Add a searchID, increment on each searchOnInput()
• Query results are now stored in a local variable and only updated if the this.searchID matches functions local searchID
• All searches are run through searchOnInput() which sets the ID properly before calling the debounced search()

Example: Sometimes searching for apple resulted an incorrect list of results with the first search on a returning after the final search for apple

This is a minor, but very confusing, annoyance on one of the main functions of the site. If this results in more issues we can discard this.

---

This change is 

[leoetlino]

can we just compare the search query instead of comparing IDs?

[savage13]

Sounds good to me, as this.searchQuery already exists