{"action":"created","issue":{"url":"https://api.github.com/repos/typestyle/typestyle/issues/200","repository_url":"https://api.github.com/repos/typestyle/typestyle","labels_url":"https://api.github.com/repos/typestyle/typestyle/issues/200/labels{/name}","comments_url":"https://api.github.com/repos/typestyle/typestyle/issues/200/comments","events_url":"https://api.github.com/repos/typestyle/typestyle/issues/200/events","html_url":"https://github.com/typestyle/typestyle/issues/200","id":268087008,"number":200,"title":"Take out css definitions to separate lib","user":{"login":"whitecolor","id":736697,"avatar_url":"https://avatars2.githubusercontent.com/u/736697?v=4","gravatar_id":"","url":"https://api.github.com/users/whitecolor","html_url":"https://github.com/whitecolor","followers_url":"https://api.github.com/users/whitecolor/followers","following_url":"https://api.github.com/users/whitecolor/following{/other_user}","gists_url":"https://api.github.com/users/whitecolor/gists{/gist_id}","starred_url":"https://api.github.com/users/whitecolor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whitecolor/subscriptions","organizations_url":"https://api.github.com/users/whitecolor/orgs","repos_url":"https://api.github.com/users/whitecolor/repos","events_url":"https://api.github.com/users/whitecolor/events{/privacy}","received_events_url":"https://api.github.com/users/whitecolor/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-10-24T15:51:18Z","updated_at":"2017-11-05T21:46:08Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Typestyle has good css props typings with docs. This could be also used for some other libraries related to css.\r\n\r\nOne of the use cases: https://github.com/snabbdom/snabbdom/issues/339\r\n\r\nWhat do you think about taking out css props definitions to separate lib, and reuse it in typestyle?\r\n\r\nPS. This is a successful issue number =)"},"comment":{"url":"https://api.github.com/repos/typestyle/typestyle/issues/comments/342008422","html_url":"https://github.com/typestyle/typestyle/issues/200#issuecomment-342008422","issue_url":"https://api.github.com/repos/typestyle/typestyle/issues/200","id":342008422,"user":{"login":"whitecolor","id":736697,"avatar_url":"https://avatars2.githubusercontent.com/u/736697?v=4","gravatar_id":"","url":"https://api.github.com/users/whitecolor","html_url":"https://github.com/whitecolor","followers_url":"https://api.github.com/users/whitecolor/followers","following_url":"https://api.github.com/users/whitecolor/following{/other_user}","gists_url":"https://api.github.com/users/whitecolor/gists{/gist_id}","starred_url":"https://api.github.com/users/whitecolor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whitecolor/subscriptions","organizations_url":"https://api.github.com/users/whitecolor/orgs","repos_url":"https://api.github.com/users/whitecolor/repos","events_url":"https://api.github.com/users/whitecolor/events{/privacy}","received_events_url":"https://api.github.com/users/whitecolor/received_events","type":"User","site_admin":false},"created_at":"2017-11-05T21:46:08Z","updated_at":"2017-11-05T21:46:08Z","author_association":"CONTRIBUTOR","body":"> If the cost of updating definitions stayed the same as it is today, then I'd have no objection.\r\n\r\nMostly if you need to update css props you will just have to update one package, update it version and publish. Typestyle package itself may depend on `~1.x.x` version so there will be no need update it until there is some breaking change in props definitions or something like that that will cause major version change. Though typestyle functionality itself almost doesn't dependepend at all on css props definitons.\r\n\r\n> depending on typestyle but only using the types\r\n\r\nThis quite ok, but still requires some potentially unnecessary deps. And also there is special  `$unique` field in CSS props specific for `typestyle`."}}
{"actor":{"display_login":"whitecolor"}}