Skip to content

automatic mixin namespacing (for less) #5

Open
davidpfahler opened this Issue Dec 18, 2012 · 0 comments

1 participant

@davidpfahler
excellenteasy member

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.