This repository was archived by the owner on Aug 9, 2022. It is now read-only.
Do not disable CSS/JS aggregation on dev environments #7
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We had CSS/JS aggregation disabled on Dev when we were developing HEKS. This regularly leaded to client reporting "new feature does not work" issues. We always replied with "clear browser cache" and this fixed the issue.
This happened too often, so we decided to enable CSS/JS aggregation on Dev and disable it locally in local.settings.php. Client testing improved much after that.
If you commit this, I'll do the same changes for d8-starter.