Propagate digested paths for asset files from v3 to v2 #499
+120
−0
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
…d assets.resolve_assets_in_css_urls configuration option to allow disabling AssetUrlProcessor
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.
Propagate 2 asset-url fixes from
v3tov2assets.resolve_assets_in_css_urlsconfiguration option to allow disablingAssetUrlProcessor#489 Add assets.resolve_assets_in_css_urls configuration option to allow disabling AssetUrlProcessorWe would like to use https://github.com/rails/dartsass-rails gem in our app.
But we are not yet ready to upgrade sprockets to
V3and usemanifest.jsbecause of complex structure of our assets folders.These 2 fixes in
V2allow us to usedartsass-railsgem withsprockets V2and make asset urls work fine in dev. As well as pre-compile them for production