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
I have a Server Side Pagination implementation in my Angular 13 application that uses Akita 7
I've implemented the steps in documentation perfectly, and everything is working as expected.
However, when I do some create, update and delete operations, the paginatorRef fails to reflect this. It reflects the changes after I refresh the page, and I don't want that!
By trial and error, nothing worked, and I came upon this cacheTimeout thing and I see that it accepts an Observable<any>.
This seems to be like a perfect solution, where I would invalidate the cache by emitting an event via an Observable as soon as I do some create, update and delete operations, instead of using the interval(10000) given by the Akita docs here: https://opensource.salesforce.com/akita/docs/plugins/pagination/#cachetimeout
But there is a small problem, I don't know how to specifically implement cacheTimeout in my app.
This discussion was converted from issue #1004 on January 09, 2023 07:28.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a Server Side Pagination implementation in my Angular 13 application that uses Akita 7
I've implemented the steps in documentation perfectly, and everything is working as expected.
However, when I do some create, update and delete operations, the paginatorRef fails to reflect this. It reflects the changes after I refresh the page, and I don't want that!
By trial and error, nothing worked, and I came upon this
cacheTimeout
thing and I see that it accepts anObservable<any>
.This seems to be like a perfect solution, where I would invalidate the cache by emitting an event via an
Observable
as soon as I do some create, update and delete operations, instead of using theinterval(10000)
given by the Akita docs here: https://opensource.salesforce.com/akita/docs/plugins/pagination/#cachetimeoutBut there is a small problem, I don't know how to specifically implement
cacheTimeout
in my app.Hopefully somebody knows...
Beta Was this translation helpful? Give feedback.
All reactions