We deprecated the current behavior in 3.0 with a warning and will remove the default assumption that @import intends to import any missing file with no extension as css in the next release.
Please watch your application log for deprecation warnings. chris On Sat, Aug 28, 2010 at 12:57 PM, Chris Smeder <csme...@gmail.com> wrote: > I am using multilevel imports similar to Chris Eppstein's file > structure > http://chriseppstein.github.com/highlighted/stylesheets/screen.sass.html > however, I am finding it hard to track down import errors. For example > in my _application.sass file I had written: > > @import applicaton/header > @import applicaton/footer > @import applicaton/page > > (missing the "i" in application) > > Sass didn't throw an error. I had to hunt down the issue. I am worried > I will make a similar error with out catching it right away. Is there > any way to make sass throw an error into the erb file with a stack > trace when an import doesn't work? Similar to how it throws an error > when you call a mixin with the wrong number of arguments. > > -- > You received this message because you are subscribed to the Google Groups > "Haml" group. > To post to this group, send email to h...@googlegroups.com. > To unsubscribe from this group, send email to > haml+unsubscr...@googlegroups.com <haml%2bunsubscr...@googlegroups.com>. > For more options, visit this group at > http://groups.google.com/group/haml?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to h...@googlegroups.com. To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
