Remind users to clear the cache after config changes - #136
Merged
Conversation
`tailwind:init` and `tailwind:update` write `config/packages/symfonycasts_tailwind.yaml`, but the container caches that config, so a later `tailwind:build` won't pick up the new `binary_version` until the cache is cleared. Both commands now tell the user to run `cache:clear`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
tailwind:initandtailwind:updatewriteconfig/packages/symfonycasts_tailwind.yaml, but the container caches that config — so a latertailwind:buildkeeps using the oldbinary_versionuntil the cache is cleared. That's what bit the reporter in #135: they chose v4 duringinit, butbuildstill downloaded v3.14.Both commands now warn the user to run
php bin/console cache:clearafter writing the config.Closes #135