Joshua Christman
Joshua Christman
I agree - Having a method of "netsting" classnames would allow for more specificity. As of right now, this generates an error, because "custombutton" is not one of the whitelisted...
I'm not quite sure that will work for all project structures. For example, assume the following project structure: ``` client/ configs/ themes/ index.js
Is the `@prepend` syntax easier to support than allowing nested classes? What if this generated the same CSS as the `@prepend` syntax? ``` js const styles = cssInJS({ mytheme: {...
Oh I see what your main use case was. Is the idea that `.my-theme` is defined somewhere and then the `@prepend` would be defined somewhere else?
+1 -- seems like a really nice kit. Any plans for public source code release or further maintenance?
If you wanted to open source it in the meantime, I’m sure members of the community could submit pull requests with fixes for some of these open issues...
https://www.npmjs.com/package/@livechat/ui-kit seems to indicate this is now MIT licensed. Not sure when that happened
@jasonnathan, I got tired of waiting for him to merge my pull request and have created a new atmosphere package based on my fork of this repository. I think you...
+1 please merge the solution. I am having this same problem.
Error with code. See my comments on the PR.