Outstanding Issues to Address

[spencer516]

Open Questions:

• [x] ~Is the .css-compose file extension the right route to go? What are the pros/cons?~
• [ ] Is the @compose with nested @ sufficient?
• [x] What happens when we want to use dynamically generated class names? (this is possible, it just needs to be properly documented when/why).
• [x] What versions of Ember does this work with? (It's untested against everything except 2.10)
• [x] ~Need to support back to node 0.12 (probably not necessary).~
• [x] this should not be a relative path
• [x] this should also probably not be hard-coded.
• [ ] What do we do about composes definitions that are declared multiple times? And, what are the ordering concerns, if any, we need to think about?

Possible Improvements / Ideas

• [ ] What are the possible errors or easy mistakes people might make if they're using this?
• [ ] If we're doing a production build, can we remove the _classify hooks/helpers so that a string is replaced wholly with another string? (Will that even matter? ¯_(ツ)_/¯)
• [ ] Since creates an "adapter" between the CSS from the JS, what other things can we do to analyze/transform the CSS so that it does not break the app? (e.g.: removing unused styles, merging repeated styles, minifying class names?)