alertmanager/ui
stuart nelson 4f8ef26b28 Update matching algorithm (#910)
* Test for consecutive chars throughout string

Previously, we were only testing for consecutive
characters at the beginning of the string. Now,
the entire string being compared is searched
through for a matching character, and then the
consecutive search starts.

We were seeing weird situations where the text
entered matched the last half of certain terms,
but because it wasn't, but because we only
searched from the start, results that probably
shouldn't have been the top suggestion were being
suggested too high on the list.

* Weight consecutive matches more highly

Bit of a guess, this seemed to give better results
for my small test case.

* bindata
2017-07-19 11:50:33 +02:00
..
app Update matching algorithm (#910) 2017-07-19 11:50:33 +02:00
lib Serve FontAwesome & Bootstrap ourself 2017-06-07 22:40:18 +02:00
Dockerfile Fix external web url (#836) 2017-06-07 22:38:39 +02:00
bindata.go Update matching algorithm (#910) 2017-07-19 11:50:33 +02:00
web.go Serve FontAwesome & Bootstrap ourself 2017-06-07 22:40:18 +02:00