Closed devraj closed 6 years ago
We don't allow you to disable digesting in 3.0. It still being listed as an option is the bug here. The lack of digesting only forces us to hack Sprockets, and it doesn't provide any useful benefit.
@envygeeks so does that mean there would be no way of exposing an asset with a particular "fixed" name? e.g /assets/screen.css
?
Why would you want that?
The feature required us to maintain a lot more than I wanted to, and to consider a lot more than I wanted to. Sprockets doesn't support what you want which meant I had to take over parts of Sprockets to get what you wanted in 2.x.
If somebody is willing to monetarily sponsor it's initial development and testing, I'm happy to add it into the new rewrite, other than that though I feel it would take too much development time.
The reason why is because now we have to write code that works with Sprockets 3, and 4. Can be back ported and supported for at least a year, with minimal effort, and can integrate into our workflow which is much more well designed than Assets 2.x
@envygeeks Anomaly would be willing to consider sponsoring it, do you want to drop us a line and carry on the conversation there?
They @devraj there are so many ways to contact ya'll I don't know which is best. It might be easier if ya'll email me at jordon at envygeeks.io, I'll be available for the next few hours if you want to chat over the phone too, if that's easier.
Description
Lodging this as a bug after me trying this on two production Jekyll installs. The
digest
setting is set tofalse
but still produces the digest on the asset file names.Steps
The following is how my Jekyll site is setup with
jekyll-assets
version3.0.2
along sidejekyll
version3.6.2
relevant configuration as follows:Gemfile
for the site_config.yml
extract:Output
Expected
Files being written without the digest.