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'm trying to retrieve list items and choice column values from a list. I expect that when I have caching enabled .using(Caching(...)) that it stores cached data in my local storage (now that I type this, I haven't tested changing it to session storage) and reads it on subsequent calls.
Observed Behavior
What I see is:
3.21
Works as expected with all caching and even paged results. Thanks to the following bug report, I see paging was fixed as of 3.21 #2836 and it works great! All other paging works as expected. I can see the cached data written to local storage and it is read correctly. Paged results even retrieve their "getNext()" results correctly (thanks again for that fix in 3.21!).
3.22
This version doesn't cache at all unless the request has paging. If my item retrieval request has paging, it will store data to the cache. If not paging, nothing is stored regardless request type.
If trying to load a paged cache request, an infinite loop with getNext() will occur as it feels like it never fetches the next bit in the cache and therefore never changes its "hasNext" property to false.
This version is completely broken with caching.
Steps to Reproduce
We are using a huge shared library in house. There are many things that are spread between multiple files and classes. So I'll just copy the imports here and then just copy/paste the main functions.
Please see "Observed Behavior" above as that outlines what I'm experiencing. Basically using the same code with 3.21 works yet it completely fails with 3.22 (regarding caching).
Major Version
3.x
Minor Version Number
3.22
Target environment
SharePoint Framework
Additional environment details
Expected or Desired Behavior
I'm trying to retrieve list items and choice column values from a list. I expect that when I have caching enabled .using(Caching(...)) that it stores cached data in my local storage (now that I type this, I haven't tested changing it to session storage) and reads it on subsequent calls.
Observed Behavior
What I see is:
3.21
Works as expected with all caching and even paged results. Thanks to the following bug report, I see paging was fixed as of 3.21 #2836 and it works great! All other paging works as expected. I can see the cached data written to local storage and it is read correctly. Paged results even retrieve their "getNext()" results correctly (thanks again for that fix in 3.21!).
3.22
Steps to Reproduce
We are using a huge shared library in house. There are many things that are spread between multiple files and classes. So I'll just copy the imports here and then just copy/paste the main functions.
Please see "Observed Behavior" above as that outlines what I'm experiencing. Basically using the same code with 3.21 works yet it completely fails with 3.22 (regarding caching).
Get list items. Uses paging.
Get choice column values
The text was updated successfully, but these errors were encountered: