This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-02
Channels
- # aleph (14)
- # boot (4)
- # cider (3)
- # clara (1)
- # cljs-dev (62)
- # cljsrn (20)
- # clojure (81)
- # clojure-berlin (2)
- # clojure-russia (76)
- # clojure-spec (35)
- # clojure-turkiye (1)
- # clojurescript (84)
- # cursive (2)
- # data-science (6)
- # datomic (4)
- # hoplon (92)
- # lumo (35)
- # om-next (1)
- # pedestal (2)
- # re-frame (2)
- # reagent (36)
- # ring-swagger (10)
- # unrepl (30)
- # untangled (124)
Hello all. I was studing how to use http://cljsjs.github.io/ in reagent project, but I couldn´t figure out. Is there the same as you use .js included in html and using the lib as js/<library export>
?
Seems like so to me, I use localforage for example https://github.com/YurySolovyov/eion/blob/master/src/eion/bindings/storage.cljs
What does the symbol “:>” refer to?
heya! I'm just starting with svg in reagent; is there a better way to draw paths than with a huge string e.g. [:path {:d "M 30,40 C 100,40 50,110 120,110"}]
? it's awfully cumbersome to compose that string 😞
@stuartrexking basically [:> react-component ...]
, I wrote about the pattern https://opensourcery.co.za/2017/02/12/using-semantic-ui-react-with-re-frame/
Thanks. I figured it out. Is this something that should /will be in the docs?
it definitely should
I've created a "wishlist" issue to write an actual user's manual for reagent
Ah, thank you very much both @kennethkalmer and @peterhazy
but haven't worked on it because I'm lazy
It’s a good list though.
any idea if this is going to be fast enough? https://gist.github.com/YurySolovyov/834e9cd6258f36d6f333fd3d0806c238
@daiyi yeah, I'm afraid that's all you have when using SVG paths.
ok, I didn't found class-names, so I've written my own FWIW -> https://github.com/YurySolovyov/class-names-cljs
I mean, the one you didn't find
well, that one is for JS
@pesterhazy I didn't want to have to cast maps to objects or use special syntax
to interoperate
I understand the rationale, I was just checking that that's what you're referring to
yes, correct, my was inspired by this one
it would be cool if reagent supported than natively
[:div {:class ["foo" "bar" :baz]}]
something like that
I'm happy to upstream it if that's ok with reagent guys
IMO it wouldn't hurt to add your function, or something like it, to reagent.core
or even to add a special check for the class
prop - though maybe that's a bit too much magic?
I'll fill the issue
I mean we already support [:div.foo {:class "bar"}]
so the additional check for (seq? class)
may not be too much trouble: https://github.com/reagent-project/reagent/blob/master/test/reagenttest/testreagent.cljs#L301