Skip to content

automatic mixin namespacing (for less) #5

Description

@davidpfahler

When #3 is solved, the importing of different less files can cause conflicts if mixins have the same name. The dependency tracking should be able to tell which mixin each call refers to and can then automatically namespace them, before the compiler is involved.

To Do:

  • copy files that would be modified to a tmp/ folder
  • surgically insert namespaces before conflicting mixins
  • use the tmp/ files in the main file (given to the compiler) instead of the original ones

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions