Remove composer drupal optimizations #221
Merged
Conversation
This file contains 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
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.
GitHub Issue: #217
We found that trying to allow composer plugins manually didn't work, so since Drupal has updated their recommended project, the only plugin causing problems is the composer optimizations, which was (AFAIK) created for Composer 1.
What does this Pull Request do?
remove
zaporylie/composer-drupal-optimizations:^1.1What's new?
(i.e. Regeneration activity, etc.)? no
How should this be tested?
Without this PR: vagrant up fails when installing composer dependencies because composer does not allow plugins
with this PR: Vagrant up (or provision) completes successfully.
Additional Notes:
Any additional information that you think would be helpful when reviewing this
PR.
Interested parties
Tag @alxp