Fix the resultsdb frontend search
ClosedPublic

Authored by jskladan on Oct 14 2016, 11:59 AM.

Details

Summary

Added suggestions for the testcase field using Twitter typeahead library.
There are also some other changes in the javascript, to make the search
work in a better way.

Test Plan

Tested manually

Diff Detail

Repository
rRSFE resultsdb_frontend
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
jskladan retitled this revision from to Fix the resultsdb frontend search.Oct 14 2016, 11:59 AM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
garretraziel accepted this revision.Oct 14 2016, 12:19 PM

I haven't tested it, but code looks OK and we've tested on @jskladan's computer that it works and behaves allright.

This revision is now accepted and ready to land.Oct 14 2016, 12:19 PM

Not a huge fan of the GLOBAL stuff. Is there any other sane way to get the same thing done?

In D1027#19323, @tflink wrote:

Not a huge fan of the GLOBAL stuff. Is there any other sane way to get the same thing done?

Not that I know of. We could use flask-cache extension instead, but it just does the same thing, only in a way that you don't see, or we could set-up a memcached service, but that hardly seems like it's worth the trouble.

tflink accepted this revision.Oct 17 2016, 3:46 PM

I don't see anything else that concerns me. I'd like to do the frontend in a different way someday but that day is not today and there are bigger fish to fry :)

Closed by commit rRSFE22f0558d8992: Fix the resultsdb frontend search (authored by Josef Skladanka <jskladan@redhat.com>). · Explain WhyOct 18 2016, 8:25 AM
This revision was automatically updated to reflect the committed changes.