Skip to content
New issue

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

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

Already on GitHub? # to your account

Set own cache version #2

Open
giolvani opened this issue Feb 9, 2015 · 1 comment
Open

Set own cache version #2

giolvani opened this issue Feb 9, 2015 · 1 comment

Comments

@giolvani
Copy link

giolvani commented Feb 9, 2015

It would be nice, if I could set my own version cache.
This way I could be more control of my application.

instead

<link href="/css/styles.css?~v=Iz7DDyL6DCDnT_L414h7aec4VUNOlN9dDYVRGoD2ZB01" rel="stylesheet"/>
<script src="/js/app.js?~v=QWNK55__txkMIVFvtdF3fy5lDLK7GLkwLzP8nzCV6nw1"></script>

could be

<link href="/css/styles.css?~v=123abc" rel="stylesheet"/>
<script src="/js/app.js?~v=123abc"></script>

Thank you!

@kemmis
Copy link
Owner

kemmis commented Feb 14, 2015

@giolvani This is definitely possible to implement, but I don't really see the purpose / usefulness of this. The whole point of this transform is to automatically manage the cache busting for you. If you set the version to something static, then you'd have to update that value manually every time you change anything in the bundle contents.

I could see maybe providing an optional delegate parameter that would allow anyone to override the hash generation logic. That would allow you to set a static string for the hash, or perhaps use an alternate hashing algorithm.

Thoughts?

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

No branches or pull requests

2 participants