Keep original filename patterns #2
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the plugin has output filenames hardcoded to
'assets/[name].[ext]?v=[hash]'
. This PR would allow custom filename conventions by transforming the configured options instead of overwriting them. It detects the length of the hash and intelligently moves it to the query part, unless already set up correctly.A few examples how the filename patterns are transformed:
assets/[name]-[hash].js
assets/[name].js?v=[hash]
assets/[name]-[hash].[ext]
assets/[name].[ext]?v=[hash]
assets/[name].[ext]
assets/[name].[ext]?v=[hash]
assets/[name]-[hash].[ext]
assets/[name].[ext]?v=[hash]
assets/[name]-[hash:10].[ext]
assets/[name].[ext]?v=[hash:10]
assets/[name]-[hash][extname]
assets/[name][extname]?v=[hash]
assets/[name]-[hash:10][extname]
assets/[name][extname]?v=[hash:10]
assets/[name].js?v=[hash]
assets/[name].js?v=[hash]
assets/[name].[ext]?v=[hash]
assets/[name].[ext]?v=[hash]