-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add cache handling #168
Comments
I will try to think about this topic - I have recently played around with yet another cachebuster concept - Easter weekend is coming - maybe I find some time 😄 |
Initially, I thought that having a custom task appending some hash to the build bundle (e.g. Additionally,
...that need to be considered for a cache-handling mechanism as well. |
Did you have a look into the |
Hi Peter, i checked the I could image though that the option of self-contained bundles with unique file names could still come handy, e.g. thinking of more advanced service worker based caching strategies (offline-first use cases etc) - but perhaps that is more of ui5-tooling topic... |
Regarding service workers and self-contained bundles, you may look into the I'll close this issue for now... Thanks for all your inputs and thoughts... Appreciate it and if you have more, just let me know... 😄 |
Thank you for this showcase project. It comes very handy. 👍
This is an enhancement request. As resource caching is a central issue in todays web applications, it would be nice to add cache-handling to the best-practice-showcase project. Ideally, such a cache handling would take in to account more advance use-cases that are possible with the ui5-tooling, such as custom bundles.
The text was updated successfully, but these errors were encountered: