@import should handle .css.less files about less-rails HOT 3 CLOSED

If it is possible, I am all for it. But I am not sure not it is since we have to bridge a gap with with a JavaScript interpreter, not a Ruby one. The way the context is setup for the JavaScript bridge, there is no way to bridge that multiple times to make several requires stitch it all together. We have to relay on the single JavaScript context and let Less.js do it.s thing.

Still I am open minded if possible. Especially as things like ExecJS is used vs therubyracer for less.rb and perhaps when sprockets and/or both move to being able to do CommonJS, etc. Well above my skills at the moment.

from less-rails.

But I am not sure not it is possible since we have to bridge a gap with with a JavaScript interpreter, not a Ruby one.

Right. So you can't just call into Ruby code from LESS.

Perhaps you want to bring this up with the Sprockets folks, just to keep them in the loop? less-rails is the most important/popular non-Rails-standard asset handler I can think of, so it can't hurt to keep them informed. And maybe they have some idea.

from less-rails.

Hey @joliss, finally cleaning up some tickets.

With Sass, the following statements in application.css.scss seem to be equivalent:
@import "test";
//= require test

This is false. When you import, you are in Less/Sass land and you get all the benefit of that template engine. For example, in Sass's extensions on @import, that file will add to the rendering context of the file that imported it. It benefits from additional helpers, variables, etc. This is not true in a sprockets require.

Here is a gist that adds a test case and shows what you want done. It yields the following error: Less::Error: 'stupid_filename.less' wasn't found

There is no benefit here and it is fighting an uphill battle. First, you would have to convince the less maintainers it is a good idea, but for what benefit? When you break it down the only need for a .css.less file is to start off the hint to Sprockets that xyz template engine will be used. From there on down, it is Turtles Engine rendering all the way. Hence, keep with their constraints and enjoy the few extras like asset helpers that are provided.

BTW @joliss it was super great to hang out at JSConf!!!!

from less-rails.