In a Rails 3.1 app, one controller needs to have all its views compile whatever Sass stylesheets they might need per request using a set of custom variables. Ideally, the compilation must happen via the asset pipeline so that content-based asset names (ones that include an MD5 hash of the content) are generated. It is important for the solution to use pure Sass capabilities as opposed to resorting to, for example, ERB processing of Sass stylesheets.
From the research I’ve done here and elsewhere, the following seems like a possible approach:
-
Set up variable access
-
Create some type of variable accessor bridge using custom Sass functions, e.g., as described by Konstantin Haase here (gist). This seems pretty easy to do.
-
Configure all variable access via a Sass partial, e.g., in
_base.sasswhich is the Compass way. The partial can use the custom functions defined above. Also easy.
-
-
Capture all asset references
-
Decorate the
asset_pathmethod of the view object. I have this working well. -
Resolve references using a custom subclass of
Sprockets::Environment. This is also working well.
-
-
Force asset recompilation, regardless of file modification times
-
I have not found a good solution for this yet.
-
I’ve seen examples of kicking off Sass processing manually by instantiating a new
Sass::Engineand passing custom data that will be available inSass::Script::Functions::EvaluationContext. The problem with this approach is that I’d have to manage file naming and paths myself and I’d always run the risk of possible deviation from what Sprockets does. -
I wasn’t able to find any examples of forcing Sprockets processing on a per-request basis, regardless of file mod times, that also allows for custom variable passing.
-
I’d appreciate comments on the general approach as well as any specific pointers/suggestions on how to best handle (3).
Sim.
It is possible. Look here SASS: Set variable at compile time
I wrote a solution to address it, I’ll post soon and push it here, in case you or someone else still need it.