This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-29
Channels
- # architecture (2)
- # bangalore-clj (2)
- # beginners (177)
- # boot (1)
- # cider (36)
- # clara (15)
- # cljs-dev (30)
- # cljs-experience (6)
- # cljsrn (7)
- # clojure (94)
- # clojure-argentina (2)
- # clojure-brasil (1)
- # clojure-dusseldorf (6)
- # clojure-greece (1)
- # clojure-italy (18)
- # clojure-norway (4)
- # clojure-quebec (1)
- # clojure-russia (28)
- # clojure-sg (3)
- # clojure-spec (12)
- # clojure-turkiye (1)
- # clojure-uk (12)
- # clojurescript (169)
- # code-reviews (4)
- # community-development (2)
- # core-async (6)
- # core-matrix (6)
- # cursive (35)
- # datomic (18)
- # devcards (4)
- # euroclojure (1)
- # hoplon (2)
- # keechma (4)
- # klipse (2)
- # leiningen (1)
- # luminus (16)
- # mount (1)
- # off-topic (34)
- # om (31)
- # pedestal (6)
- # re-frame (14)
- # reagent (33)
- # specter (4)
- # uncomplicate (8)
- # unrepl (15)
- # untangled (24)
- # yada (25)
@tony.kay The om-css snapshot seems awesome. Surprised by the fast fix in om-next multi-method. but then saw that you fixed it 🙂
If in the server I add a om.next then it affects the cljs advanced build for some reason 😞
The easiest way to replicate it is just to add [om.next :as om]
in the require of the (ns user
of user.clj
then when i do lein clean && lein cljsbuild once release
I get the html without the class just <li>
and the <style id="my-css"></style>
is empty.
Managed to replicate it in the cookbook example, just by importing in .clj om next. If I remove the import the production build works just fine.
Hey @claudiu and other Untangled/om-css
users out there. I am currently working with the new version of this library and i'm facing some issues that i would like to improve. Would love to hear your thoughts and suggestions on this.
First of, local css-rules and global css-rules are now separated by different protocols. But there are some cases where you would want to add additional css-rules to a classname, for example when you are using an another external component. So what i basically mean is that you have some cases where you want to prevent a keyword to be localised even though it is defined somewhere nested in your local-rules. My suggestion would be to prefix those keywords with a $
.
Second, multiple classnames now have to be defined like this:
{:className (str classA " " classB " " (when condition classC))}
I think it would be nice to have a helper function that takes any amount of classnames and merges them together.
{:className (css/merge-classnames classA classB (when condition classC))}
@timovanderkamp I agree with (1). On (2): I like the idea (though ppl have prob written their own, it won’t hurt to include one). The name is the primary thing. Something shorter would be nice.
probably should go through the docs and explore what we’re going to run into. Or, we can add them as people run into them. The latter makes the library a bit more frustrating.
I've looked at the garden selectors to check what would be a problem atm. At a quick look it would not be possible yet to use the CSS combiners and the special selector &.
The CSS combiners are +, - and >
[:.a {..}
[:+.b {..}]]
->
.a {
..
}
.a + .b {
..
}
What doesn't work atm is that [:+.b {..}]
won't be transformed to [:+.namespace_Component__b {..}]
, as it should be
same goes for all the CSS combiners
I’m betting one generalization that scans for the set of these like #{"+" ">" ...}
will get us a long way
yes exactly, we are currently only transforming keywords that start with :.