There are a few things I don't like about import-anywhere, in addition to Chris's comments. First, I don't like that it suddenly matters which styles are in which file. Everywhere else in Sass (and CSS), as long as you import files together, which styles are in which file is irrelevant.
Also, allowing imports not at top-level means that you can have invalid Sass files that still work when being imported (e.g. ones that only contain properties). That said, the latter issue could potentially be checked for, and if you think about files as separate stylesheets it's nice to be able to use those in a scoped way. I'm potentially open to being convinced. On Mon, Dec 14, 2009 at 12:17 PM, Chris Eppstein <[email protected]>wrote: > On Mon, Dec 14, 2009 at 12:12 PM, Jacques Crocker <[email protected]>wrote: > >> Mixins work great, but not for everything. When you already have some >> styles somewhere and you need to reuse it scoped on another page, cleanest >> way would be to just import the file nested within another style rule. >> > > No, that would be the fastest way. The cleanest way, in my opinion is to > refactor given your new usage requirements. > > chris > > -- > You received this message because you are subscribed to the Google Groups > "Haml" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected] <haml%[email protected]>. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
