Instead of generating a paginated result from an unsorted list of patches, we should try to sort all patches (and issues in a follow up) by their latest timestamp on the database and then in the tauri command paginate the sorted list, so we can provide a infinite loading with a natural order.
In a follow up it would probably also make sense to generate sql statements according to the thing we want cobs to order by
Instead of generating a paginated result from an unsorted list of patches, we should try to sort all patches (and issues in a follow up) by their latest timestamp on the database and then in the tauri command paginate the sorted list, so we can provide a infinite loading with a natural order.
In a follow up it would probably also make sense to generate sql statements according to the thing we want cobs to order by
@rudolfs so one thing I realized with this patch, is that Iām sorting patches by the last revision on each patch, which in itself is a nice feature.
The other option would be to sort by the first revision which opened the patch, but this would mean that sometimes a new revision to a patch would still not show up on the top.
wdyt?
EDIT: Ok so I pushed revision 81e5088 which changes this so we order by the timestamp a patch as been opened at.
Okay so I changed my mind and I think that we should sort the patches by the timestamp when they have been opened and not when the last revision on them happened.
EDIT: Ok so I pushed revision 81e5088 which changes this so we order by the timestamp a patch as been opened at.
Think this makes the most sense.
Rebase.
Build is failing though. Otherwise code and functionality LGTM.
š Workflow runs š Branch on GitHub
Fix e2e tests
Okay so tests are passing now