Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Deprecate asset fallback #375
When an asset isn't found the behavior is to pass the string through. For example a valid asset will return a url from pipeline
While if you make a typo, you won't get an error or anything, it just falls through:
Hopefully I don't have to elaborate on why this is bad.
This PR is a child PR to one in Rails that will introduce a
There are valid reasons for not using the asset pipeline, if you have a purely static asset in the public folder or if you want to link to a static URL in your assets somewhere it makes sense to declare that intention. Eventually we will replace the behavior of the deprecation with an exception so people don't lose hours of their to typos.
We only emit the deprecation when a
Sep 1, 2016
I know it's been a long time since this PR was merged. Is there any chance we could get an update to the section of the Rails Guides that addresses asset fallback?
I'd be glad to submit a PR with the approval of the team (but otherwise, I'm reluctant to spend any time on it).