Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Persisting SCSS variables in rails asset pipeline?

I'm upgrading a rails app with lots of SCSS stylesheets to use the asset pipeline, and need to include some global variables and mixins for each file.

Adding several @import directives at the top of every file isn't very DRY, so I'd like to do something like this:

# application.css
/*
*= require variables
*= require mixins
*= require_tree .
*/

This doesn't work of course, because the variables are not persisted across files. Anyone know how to achieve this?

like image 935
Zubin Avatar asked Jan 16 '12 23:01

Zubin


3 Answers

The default manifest syntax isn't powerful enough to give you useful Sass features like shared variables, mixins, etc. Instead, you should:

  1. Rename application.css to application.scss (or application.css.scss in Rails 4 or earlier)
  2. Instead of using the

    /*
     *= require variables
     *= require mixins
     *= require_tree .
     */
    

    nonsense, you should now use

    @import "variables";
    @import "mixins";
    @import "blah"; // import each SCSS file in your project like this.
    

    This will ensure you have full benefit of your variables and mixins throughout your project, and you are kept as DRY as Sass allows.

like image 78
Adam Bowen Avatar answered Oct 18 '22 23:10

Adam Bowen


Simply importing the necessary file from each Scss or Sass file seems to have worked for me. For example, I have a colors.scss file that includes some constants like this:

$black: #222;

I require it in my application.css manifest along with some other files:

/*
 *= require colors
 *= require buttons
*/

In my buttons.css.scss file, I simply do this to avoid the error:

@import "colors";
like image 23
Avand Amiri Avatar answered Oct 18 '22 23:10

Avand Amiri


Doesn't seem to be possible. Ended up prepending each file with @import 'includes/all'; and including everything else from includes/all.css.scss.

like image 4
Zubin Avatar answered Oct 18 '22 22:10

Zubin