{"action":"opened","issue":{"url":"https://api.github.com/repos/Ticketfly-UI/ember-css-composer/issues/3","repository_url":"https://api.github.com/repos/Ticketfly-UI/ember-css-composer","labels_url":"https://api.github.com/repos/Ticketfly-UI/ember-css-composer/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/Ticketfly-UI/ember-css-composer/issues/3/comments","events_url":"https://api.github.com/repos/Ticketfly-UI/ember-css-composer/issues/3/events","html_url":"https://github.com/Ticketfly-UI/ember-css-composer/issues/3","id":198202197,"number":3,"title":"Outstanding Issues to Address","user":{"login":"spencer516","id":2889608,"avatar_url":"https://avatars.githubusercontent.com/u/2889608?v=3","gravatar_id":"","url":"https://api.github.com/users/spencer516","html_url":"https://github.com/spencer516","followers_url":"https://api.github.com/users/spencer516/followers","following_url":"https://api.github.com/users/spencer516/following{/other_user}","gists_url":"https://api.github.com/users/spencer516/gists{/gist_id}","starred_url":"https://api.github.com/users/spencer516/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spencer516/subscriptions","organizations_url":"https://api.github.com/users/spencer516/orgs","repos_url":"https://api.github.com/users/spencer516/repos","events_url":"https://api.github.com/users/spencer516/events{/privacy}","received_events_url":"https://api.github.com/users/spencer516/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-30T22:39:08Z","updated_at":"2016-12-30T22:39:08Z","closed_at":null,"body":"Open Questions:\r\n\r\n- [ ] Is the `.css-compose` file extension the right route to go? What are the pros/cons?\r\n- [ ] Is the `@compose` with nested `@` sufficient?\r\n- [ ] What happens when we want to use dynamically generated class names? (_this is possible, it just needs to be properly documented when/why_). \r\n- [ ] What versions of Ember does this work with? (It's untested against everything except 2.10)\r\n- [ ] Need to support back to node 0.12 (this uses lots of new stuff that it shouldn't). \r\n\r\nPossible Improvements / Ideas\r\n- [ ] What are the possible errors or easy mistakes people might make if they're using this?\r\n- [ ] 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? ¯\\_(ツ)_/¯) \r\n- [ ] 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?)"}}
{"actor":{"display_login":"spencer516"}}