Match selector

[wlonk]

Preliminary. Pull it down and see if the filters all work for you.

[bwarren2]

Date filters work, hero and player filters work independently, I can't seem to get team and league filters to work.

Unsorted notes:

• Does this pull oldest matches first?
• Should only pull parsed matches on this page; unparsed matches don't have the necessary data.
• "Player as hero" does not seem to bind correctly, ex 85045426 as Sniper.
• Team filters don't appear to work
• I don't see html5 date selectors

Nits for later:

• If we are using player IDs rather than autocompletes, we should add the clipboard to player pages.
• Match links should probably open in a new tab

[wlonk]

Notes:

• [x] Oldest first: probably. I bet it's doing it by pk, so "roughly oldest first".
• [x] Parsed only: Will add appropriate filters.
• [x] "Player as hero": Yeah, they're independent. First pass. Will wire them together, wanted to make sure they were working first.
• [x] Teams: Huh, OK. I only had degenerate teams to test against, so my tests were bad.
• [x] Date selectors: I shake my fist at Firefox not yet supporting them. Will have to fold in JS date selectors.

Nits:

• [x] Player IDs: I wanted to use player names, but a lot of players seemed not to have any in my DB. Is that normal?
• [x] Match links: Yes, they should. They should also have clipboard icons next to them.

Also:

• [x] Hook up "enter" key.

[wlonk]

@bwarren2: try again when you can. I think it's gtg now.

[bwarren2]

Player IDs: we don't mirror the personas for players that we are not tracking, so that is semi normal.

I think some unparsed matches are still getting in? When I filter just on feeder_noob, I get a match that has her in it but is unparsed.

Otherwise, things seem to work as expected!

[wlonk]

If unparsed matches are getting in, I presume that derives from problems in the Parsed manager, then. That's how I'm filtering.