Fix asset pipeline errors for plugin dummy apps #44016
Merged
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.
To fix #43920, f292daa added
sprockets-rails
to the generatedGemfile
for engine plugins because their dummy apps use Sprockets. However, non-engine plugins exhibit the same issue because their dummy apps also use Sprockets.This commit forces
skip_asset_pipeline
to be true when a plugin is not an engine, and fixes several tests that failed to detect these issues because they were accidentally using therails/rails
Gemfile
instead of the generated pluginGemfile
.