In development - handling assets that don't exist about sinatra-asset-pipeline HOT 7 CLOSED

Sounds like a great idea. Do you have the chance to try it out and create a pull request?

from sinatra-asset-pipeline.

However, after giving it some more thought it only raises an exception in the development environment as all assets are served via the default Sinatra public folder in production. Do you still think we need the if statement?

from sinatra-asset-pipeline.

It's a very minor detail that I only noticed because I was migrating an app from rake-pipeline to this and some of our previous urls were displaying this error instead of 404'ing (or something else to tell me that the asset didn't exist). It took me a while to figure out that I had a path mis-configured.

With using sprockets-helpers you shouldn't ever be able to generate a URL to an asset that doesn't exist, so in theory it wouldn't matter too much. Only use case I could come up with is if an implementer needed their sinatra app to handle certain urls that began with "/assets" ... maybe like if they wanted to use sinatra to dynamically serve a user profile photo - "/assets/user/:id" or something. If it means anything, I think Sprocket's built-in rack middleware passes if it comes across an asset that doesn't exist, but I could be wrong.

If you think it's relevant enough to issue a PR I'll do so and test it out.

from sinatra-asset-pipeline.

Got it, I would love a pull request!

from sinatra-asset-pipeline.

Closing this issue, please reopen it if you find the time to make a pull request.

from sinatra-asset-pipeline.

I think this could still be useful, even if it were just a more explicit error message, saying which asset it was trying to find.

from sinatra-asset-pipeline.

I agree, a friend of mine using this library just ran into the same problem the other day, so I think that we should reopen this, do some work and get this feature in.

from sinatra-asset-pipeline.