-
Notifications
You must be signed in to change notification settings - Fork 11
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
CSS version replacement #7
Comments
I'd never thought of replacing the assets inside the stylesheets, I did it with just html in mind, but it would be a good feature. If the paths are all the same in the CSS then it should be doable. I'll have a tinker and will let you know how I get on. |
I've finally had a chance to check this out. I added a couple of tests for the scenario you described, expecting them to fail but they passed! So then I did a manual test of the same scenario and it still worked. I experienced the weird feeling of being disappointed that something didn't fail. Could you give any more details to help me recreate the problem? As you can see I'm struggling to find the bug. |
I added the manual test environment I created 302c979 See the /test-utils/manual-test-environment directory. Maybe you could fork and recreate the scenario there? |
I have a git repo that you can easily use to test this.
You'll notice that Here are the config options, that are found in
Thanks for your hard work Shane A. Stillwell On Monday, April 22, 2013 at 11:30 AM, techjacker wrote:
|
Just a repost of the above comment (email doesn't do correct formatting)I have a git repo that you can easily use to test this.
You'll notice that Here are the config options, that are found in
Thanks for your hard work |
Thanks for uploading the repo. Just from glancing at the config options I'm pretty sure that the wildcards are the issue. I didn't build the library with those in mind, but again they would be a cool feature and I think it would be possible to enable them although it will take a bit of refactoring to get them working. As a temporary fix I'd suggest naming each asset individually. |
Grunt takes care of expanding the wildcards. Here is what grunt expands them to assets [ 'public/test.css', 'public/test.js', 'public/scouts.jpg' ] After you run it, you can see that asset names in index.html have been updated, but test.css has not. Shane A. Stillwell On Wednesday, April 24, 2013 at 4:36 AM, techjacker wrote:
|
@shanestillwell
assets: ['*.png', '*.jpg'],
grepFiles: ['*.css']
assets: ['*.css', '*.js'],
grepFiles: ['*.htm'] |
This might be a bit tougher, but it seems that versioned files referenced in CSS are not being updated.
For example, lets say you have the following files
public/test.png
public/test.css
public/index.html
If you feed it the following options, the line
background-image: url('test.png');
does not get updated to the versioned file.The text was updated successfully, but these errors were encountered: