Date dropdown clear buttons, keyboard support

[shamoon]

This PR closes #144 , it adds:

• Clear buttons for each date field (after / before)
• Allows date field searching using keyboard input
• Shows visual feedback if date entered with keyboard is invalid
• Executes search after 'Enter' key pressed
• Swaps position of after & before (because I realized if you think of a range like From X to Y then "after" (X) comes first.

[jonaswinkler]

Thank you! I'll have a look at it later.

[jonaswinkler]

This doesn't really work. Well, it kind of does, but If I try to manually edit the year the cursor jumps back to the end and a request is made to the server, which results in a Bad Request 400. I'd rather much like the request to be made when I'm done typing.

Maybe we should try using the other date selection inputs, the one I've also used on the document editing form.

[shamoon]

Hmm, shouldn’t submit unless date is valid. Lemme look...

…

On Dec 17, 2020, at 1:03 PM, Jonas Winkler ***@***.***> wrote:  This doesn't really work. Well, it kind of does, but If I try to manually edit the year the cursor jumps back to the end and a request is made to the server, which results in a Bad Request 400. I'd rather much like the request to be made when I'm done typing. Maybe we should try using the other date selection inputs, the one I've also used on the document editing form. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[jonaswinkler]

Or rather, until exiting the field (or pressing enter).

[shamoon]

Ok I think I sorted it all. Also added a little visual feedback if the keyboard input is not a valid date and made it only submit on 'Enter'

[jonaswinkler]

When I select a date with the quick filters, close the drop down, clear all filters with the rightmost button, the dates don't get properly cleared. Open up the drop down again, and the list view reloads with the filter active again. Very strange.

[shamoon]

Ok last commit should fix that hopefully.

[jonaswinkler]

Alright, I've replaced the ngbDatepicker with a regular <input type="date">, which works just as well for selecting dates. This thing also does not fire (change) events when the input is still incomplete. Debounce on that, works. Also, when passing around date strings (which is totally fine), the infinite loop you discovered does not trigger, so I was able to get rid of the hack.

That should wrap up this issue.

Edit: I've included both the per-field clear buttons and the changed order of both input fields.