Kevin Matthews

It's been a long time but I've made some more progress over the last month or so. Originally, I was trying to avoid changing the look of the page at...

@gregorbg Thanks. For 1 I've got `Popup` working for the Tags, it's working great. For 2, I've removed the `WcaTable` component I originally had. I'll leave 3 (css issue) until...

> Regarding point 4: feel free to take a look at how our omnisearch input is implemented [here](https://github.com/thewca/worldcubeassociation.org/blob/master/WcaOnRails/app/webpacker/components/SearchWidget/OmnisearchInput.js). It's totally overkill for that specific situation, but it gives you a...

At this point, there are two main things left to do. 1. Make the string search and tag filter via the API work. @viroulep is helping with that (thanks!). The...

I've got the search/filter working - thanks @viroulep! Bonus: the original text-search only searched titles, but now it will search the body and everything else too. The minor css clean-up...

I think I've addressed the minor css issues I mentioned earlier. > If yes then I don't think there is anything more to do for that. Yes, that's the case,...

Thanks both for the feedback about the alerts. > We already have a debounce hook to "buffer" a given value, you can check how it's used [here](https://github.com/thewca/worldcubeassociation.org/blob/master/WcaOnRails/app/webpacker/components/SearchWidget/OmnisearchInput.js#L70); it should be...

> > It's currently not possible to sort the results; originally you could sort by "happened during" and "sent in digest". These don't seem that important, but I think I...

I think the following order (ie sort by the first item, then break ties with the second option, etc) would be good in most cases and reasonable in the rest:...

The result input is now working 'properly' since it has the event id passed to it (before it was always defaulting to a time field input, which is incorrect for...