Browse files

Update default Gemfile to point to sass-rails, not sass

  • Loading branch information...
1 parent 23820a2 commit c08f845c91568d993716cce14dc54543b5258242 @wycats wycats committed May 24, 2011
Showing with 1 addition and 1 deletion.
  1. +1 −1 railties/lib/rails/generators/rails/app/templates/Gemfile
@@ -7,7 +7,7 @@ source ''
<%= "gem 'jruby-openssl'\n" if defined?(JRUBY_VERSION) -%>
# Asset template engines
<%= "gem 'json'\n" if RUBY_VERSION < "1.9.2" -%>
-gem 'sass'
+gem 'sass-rails'
gem 'coffee-script'
gem 'uglifier'

3 comments on commit c08f845

khanh commented on c08f845 Jun 16, 2011

is there a reason to choose sass-rails over sass? Can you give any details about the specific differences?


For the convention sake :) So everything which is a "bridge" between two things will be appended by -rails

As you can see, jquery-rails, prototype-rails for example :)

wycats commented on c08f845 Jun 16, 2011

It's not purely for convention's sake. It's in order to provide a place for code that only makes sense in the presence of BOTH Sass and Rails. The only alternative is to do an if defined?(Foo) check in one or the other, which is pretty brittle. In addition to it being a good idea architecturally, this makes it really easy to have a repo that all stakeholders have access to and can work on. Chris Eppstein has done most of the work on sass-rails since my initial commit, even though he isn't on Rails core.

Please sign in to comment.