sass-rails breaks other, non-Rails-based sass middlewares #128

Closed
mperham opened this Issue Nov 2, 2012 · 3 comments

Projects

None yet

2 participants

@mperham
mperham commented Nov 2, 2012

I'm not able to explain this bug perfectly since I'm not an asset pipeline expert, so forgive any terminology mistakes.

I have a Rails app running the asset pipeline with sass-rails. I also am mounting a Sinatra application in that Rails app which has its own non-Rails-based Sprockets / compass middleware. sass-rails' configuration is global and breaks the Sinatra sass pipeline. I believe this bug is fixed in this branch:

https://github.com/hornairs/sass-rails/commits/localized_engine_registry

The Sinatra application is here:

https://github.com/mperham/sidekiq/blob/master/lib/sidekiq/web.rb#L16

What do you think?

@frodsan
Contributor
frodsan commented Apr 18, 2013

@mperham Is this still an issue?

@mperham
mperham commented Apr 18, 2013

No, because I pulled out all sprockets/sass-related stuff. Easier just to reduce dependencies.

@mperham mperham closed this Apr 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment