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

Conflicting docs regarding cache invalidation #818

Open
codeflorist opened this issue May 10, 2024 · 1 comment
Open

Conflicting docs regarding cache invalidation #818

codeflorist opened this issue May 10, 2024 · 1 comment
Labels
docs [Issue] Improvements or additions to documentation help wanted [Contribution] Extra attention is needed PR welcome [Contribution] Pull requests are welcome.

Comments

@codeflorist
Copy link

On https://www.storyblok.com/docs/api/content-delivery/v2/getting-started/cache-invalidation it is stated:

When using one of the official Storyblok SDKs (which are based on the storyblok-js-client), cache invalidation is handled automatically.

But looking at https://github.com/storyblok/storyblok-js-client?tab=readme-ov-file#activating-request-cache this seems to be contradicting:

The default behavior of the cache is clear: 'manual', that is, if you need to clear the cache, you need to call Storyblok.flushCache()

@alvarosabu alvarosabu added the docs [Issue] Improvements or additions to documentation label Sep 16, 2024
@alvarosabu
Copy link
Contributor

Thanks for opening this @codeflorist let me get back to the docs team about it

@alvarosabu alvarosabu added help wanted [Contribution] Extra attention is needed PR welcome [Contribution] Pull requests are welcome. labels Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs [Issue] Improvements or additions to documentation help wanted [Contribution] Extra attention is needed PR welcome [Contribution] Pull requests are welcome.
Projects
None yet
Development

No branches or pull requests

2 participants