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
{{ message }}
This repository has been archived by the owner on Apr 2, 2019. It is now read-only.
Hello,
This is probably less of an issue more of a question. I have setup pagination using infinite mode. My service returns Link headers for 'next' and 'prev'. I noticed that the next link is invoked and a fetch is fired to the service everytime which is good, however when i click previous it doesn't fire back to the service instead it loads locally cached version.
Is there any way to force the pagination to always got back to the service when prev is clicked using the infinite mode?
I need this to happen so clients always see changes being made by other users.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
This is probably less of an issue more of a question. I have setup pagination using infinite mode. My service returns Link headers for 'next' and 'prev'. I noticed that the next link is invoked and a fetch is fired to the service everytime which is good, however when i click previous it doesn't fire back to the service instead it loads locally cached version.
Is there any way to force the pagination to always got back to the service when prev is clicked using the infinite mode?
I need this to happen so clients always see changes being made by other users.
The text was updated successfully, but these errors were encountered: