-
Notifications
You must be signed in to change notification settings - Fork 54
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
Postfix #2
Comments
No, not really ... It think it has been done that way as it was the easiest to create while keeping the extension. |
This is simple enough to do with the following change to rev.js:
This successfully renames the files but breaks grunt-usemin's ability to rewrite other files to point to the new name because its |
Backwards compat isn't a big concern since it's only the built files that are affected and shouldn't matter. Better to do it now than later. |
I agree, better sooner than later. I assume it would be best for this to go in @sleeper's grunt-usemin v2.0 branch if that's imminent. If not, I'd be glad to work on a PR to master. A little care is needed during the transition since grunt-rev and grunt-usemin probably need to be upgraded in lockstep due to usemin's assumptions about rev's naming convention. |
Yes, 2.0 branch ;) |
@sleeper can you think of any reason why the format is
9e107d9d.default.txt
instead of the more readabledefault.9e107d9d.txt
? If not, we might consider switching.The text was updated successfully, but these errors were encountered: