Fix include viewStyle
assets in dynamic version generation
#436
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.
Description of the Change
WordPress uses the
version
property of ablock.json
file as the cache busting property for any style assets that are defined in it. This is okay but means you have to manually update a version parameter every time. If you don't it will use the current WordPress version as a fallback.In #281 we added some handling to toolkit which automatically generates and injects a version param if there isn't already one defined that consists of a hash of all the assets starting with
file:
.This automatically generated
version
currently only accounts forstyle
assets.viewStyle
assets are not handled and therefore don't trigger the version generation.This fixes that by also handling
viewStyle
in the same way.Props to @smwoll for raising this to me 🚀