You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a local instance with a lot of feeds and heavyLoad: true, so the refresh intervals vary significantly. This causes some posts to appear "not on top" when they are fetched because they are older than posts from other feeds.
Describe the solution you'd like
A new "sort by sequential-id / downloaded date" option would fix this.
If the ID is also de PK of the table it should also be faster.
Describe alternatives you've considered
I think I can hack a partial solution intercepting /rest/category/entries and sorting in JS using the id. It's not ideal because I would miss items that are bellow the current page size.
Thank you very much!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have a local instance with a lot of feeds and
heavyLoad: true
, so the refresh intervals vary significantly. This causes some posts to appear "not on top" when they are fetched because they are older than posts from other feeds.Describe the solution you'd like
A new "sort by sequential-id / downloaded date" option would fix this.
If the ID is also de PK of the table it should also be faster.
Describe alternatives you've considered
I think I can hack a partial solution intercepting
/rest/category/entries
and sorting in JS using theid
. It's not ideal because I would miss items that are bellow the current page size.Thank you very much!
The text was updated successfully, but these errors were encountered: