-
Notifications
You must be signed in to change notification settings - Fork 791
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
Do not fingerprint if filename contains a valid digest #714
Conversation
1283b98
to
05e893d
Compare
This is great. How convenient that we already had all the machinery to detect a valid hash! |
05e893d
to
1a0bf26
Compare
Changelog added. I also had to change the regex because it was not recognizing |
1a0bf26
to
8a61829
Compare
In the end it was not necessary to consider |
@rafaelfranca Think we could cut a point release of sprockets for this? |
We are migrating from Webpacker to |
Great work, thank you! Is there an update on the release? We need this package for migration. @rafaelfranca @brenogazzola @dhh |
You don't need anyone's release or permission to use this code! Just bundle directly: |
I suppose the goal of the comments was to also show that the community is looking forward to having these changes released. |
Yeah. I think we can release a minor release for this change. I'll do it |
Thank you @rafaelfranca, that's a lovely christmas present! |
@rafaelfranca It would amazing if you could release this change officially. |
As discussed in rails/jsbundling-rails#15, this PR prevents Sprockets from fingerprinting an asset that already contains a valid digest in its name.
It does that by changing
digest_path
inAsset
to returnlogical_path
if@name
contains a sequence of characters whose unpacked bytesize matches that of one of the valid digest classes