Refreshing not working after refresh with no results #75

New Issue

shadowfacts · 2020-01-06T19:50:51Z

shadowfacts commented

2020-01-06 19:50:51 +00:00

Probably because when the empty results come in, there is no pagination object provided and nil is used instead. We should actually keep the old pagination object because it is still accurate as there’s nothing newer.

shadowfacts added the

bug

label 2020-01-06 19:50:51 +00:00

shadowfacts added this to the Private Beta milestone 2020-01-08 00:35:40 +00:00

shadowfacts referenced this issue from a commit

2020-01-08 02:57:15 +00:00

Fix refreshing multiple times with no new data not working When the requested range has no results, no pagination data is returned, so the existing `newer` request range is replaced with nil. As there was no new data, the existing request range is still correct and should not be replaced. Fixes #75

shadowfacts closed this issue

2020-01-08 02:57:15 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: shadowfacts/Tusker#75