Skip to content

mixin namespacing #3

@derekprior

Description

@derekprior

This is more a topic for discussion/consideration than it is a bug report.

I'm using these flashes on a new project. Rather than generating a separate stylesheet for the flashes alone, I turned flashes.scss into a partial that gets imported into my main stylesheet. When I did this, a number of pre-existing mixins were overwritten. In my case, the mix-ins were defined by Compass, but it's not too hard to imagine conflicts with hand-written mix-ins.

It's simple enough to work around, with a few different options:

  1. Just keep flashes in their own stylesheet
  2. Play with the import order so the flashes get imported first then import the conflicting mixins.
  3. edit the scss to rename the mixins with a namespace prefix

I didn't bother testing #2, but it sounds like it should work. In my case, I just "namespaced" the mixins by prepending "flashes-" to the front. Do you think this is worth considering as a default?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions