Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate and eventually drop the internal cache #140

Open
cristinecula opened this issue Nov 3, 2020 · 1 comment
Open

Deprecate and eventually drop the internal cache #140

cristinecula opened this issue Nov 3, 2020 · 1 comment

Comments

@cristinecula
Copy link
Collaborator

The layers above the data-nav are in a better position to decide how to handle the data. Data-nav should be dumbed down and always render from the data that is given to it.

We should add a no-cache attribute that disables the internal cache and makes it behave as suggested.
We should also add a deprecation warning when the cache is used so we can identify views that need migration.

@cristinecula
Copy link
Collaborator Author

The no-cache attribute would work great for views that use data-service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant