Closed obydog002 closed 1 month ago
One thing we should probably additionally do is set a max date range for the replays. We currently initialize the range to be one year from today due to server load and probably don't want the persistence to undo that.
Any ideas on how you want this to look?
One thing we should probably additionally do is set a max date range for the replays. We currently initialize the range to be one year from today due to server load and probably don't want the persistence to undo that.
Any ideas on how you want this to look?
Yeah I was thinking it would either be defaulting the preferences everytime or setting a limit on the range controller. Setting a limit might be easier.
The code looks good but there are some failing tests
Adding a null check is not the way to fix the tests.
Rather you need to properly mock the filter builder in the test code so it returns mock versions of the controllers
There is still a minor issue, if no preferences have been set (i.e. empty client.prefs file) the range slider low and high values default to 0
Attention: Patch coverage is 70.58824%
with 45 lines
in your changes are missing coverage. Please review.
Project coverage is 58.34%. Comparing base (
dd9ab2b
) to head (5699227
). Report is 12 commits behind head on develop.:exclamation: Current head 5699227 differs from pull request most recent head 52bbfed
Please upload reports for the commit 52bbfed to get more accurate results.
In that case if null would be better we can make them Object property
Yes I believe so
https://github.com/FAForever/downlords-faf-client/issues/3119
Every field except for the game date filter when searching are now remembered after closing/opening the client and navigating away/to the replay search page.