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
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[x] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
It seems that v4 dropped support for module based apps: 3e92e8e
It does not expose HttpCacheInterceptorModule and useHttpCacheLocalStorage anymore. And the docs have been updated on how to use cashew in standalone Angular apps. There are no docs on how to use cashew in non-standalone apps.
Expected behavior
The docs describe how to use cashew in non-standalone module based angular apps.
What is the motivation / use case for changing the behavior?
Many (most?) Angular apps are not standalone and therefore they should be supported.
Environment
@ngneat/cashew 4.0.0
The text was updated successfully, but these errors were encountered:
To be honest, this is too simple, Angular 18 is almost the same, you just need to add the same to the Module.Providers array and that's it.
It could be included, but in general is not needed as if you have worked with Module-based and you have updated to use provideHttpClient() then you don't need that info
I'm submitting a...
Current behavior
It seems that v4 dropped support for module based apps: 3e92e8e
It does not expose
HttpCacheInterceptorModule
anduseHttpCacheLocalStorage
anymore. And the docs have been updated on how to use cashew in standalone Angular apps. There are no docs on how to use cashew in non-standalone apps.Expected behavior
The docs describe how to use cashew in non-standalone module based angular apps.
What is the motivation / use case for changing the behavior?
Many (most?) Angular apps are not standalone and therefore they should be supported.
Environment
@ngneat/cashew 4.0.0
The text was updated successfully, but these errors were encountered: