Closed rolfen closed 1 year ago
Hi @rolfen
By default the cache storage is storing all requests.
For each cached request, tags are generated based on the context of the odata response.
For your issue in particular, the library's support for odata version 2 and 3 is basic, very basic.
For odata version 2 there was no implemented way to get the context of the response.
I recently added a dumb function that returns an empty context for version 2 of odata.
Other solutions could be to disable caching using no-cache
in the api configuration.
Soon I will publish the fix (0.110.0), also I have to point out that the support for odata version 2 is very poor.
Regards
Unable to consume oData, with error "this.options.helper.context is not a function"
o-data-backend-service.ts
Call in
app-component.ts
:Init in
app-module.ts
Testing in Edge with "Allow CORS: Access-Control-Allow-origin" extension because I was getting CORS errors with oData version 2.
node v16.17.0 (Windows 10) running from inside Visual Studio Code
Node modules used in the project (output of
npm ls
):Fragment of the received oData (From the network tab in the browser console)
The preceding error (may be relevant):
The error (from the browser console):