feat: reusable filter handling #41
Loading…
Reference in a new issue
No description provided.
Delete branch "004-004-reusable-filter-handling"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Spec 4.4
Changes
Testing
Please fix title
004-004-reusable-filter-handlingto feat: reusable filter handlingAdded a couple unit tests to cover edge cases in the code...
Also I found a bug in test - the user can't type a date because the page uses the new (invalid) date too quickly to load data.
I'll try to add a unit test for this one.
See my above comments. I tried to add test cases for each edge case, but the test cases might need fixed too. The start date typing one is tricky.
@addison You might need to test again
I still get early network request when I try to type "04 01 2026"
before I can fully type 2026, it does this:
Also, just typing a
0in the start date input makes it do a network request 🤔@addison wrote in #41 (comment):
Let me check what's issue
it might be bad idea to send request on date change
Please add more test coverage and fix the bugs with requests being sent too early.
I want to send request only when "full" date is entered 😅
Maybe we should just have an extra "apply date range" button that is only shown when dates are changed? but then how to make that look good 🤔
@addison wrote in #41 (comment):
Let me see, what are the possibilities
@addison I have added debounce + validation from 1970 to now plus 10 years, tell me please if it makes sense
Wow, it works great!