This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-13
Channels
- # beginners (71)
- # boot (61)
- # clara (49)
- # cljs-dev (9)
- # cljsjs (2)
- # cljsrn (5)
- # clojure (55)
- # clojure-android (1)
- # clojure-italy (4)
- # clojure-spec (39)
- # clojure-uk (56)
- # clojurescript (69)
- # cursive (5)
- # data-science (1)
- # defnpodcast (6)
- # devcards (1)
- # duct (12)
- # figwheel (3)
- # fulcro (18)
- # leiningen (35)
- # lumo (19)
- # midje (1)
- # off-topic (22)
- # om (3)
- # onyx (23)
- # portkey (3)
- # re-frame (20)
- # reagent (23)
- # ring-swagger (6)
- # shadow-cljs (119)
- # specter (7)
- # unrepl (25)
@thosmos usually only pre-processed stuff is published on npm
. I looked over the nivo
package and they are already processed and do not require jsx
they do publish commonjs and es6. maybe try (:require ["nivo/es/components/..."])
or "nivo/lib/components/..."
i asked this on the weekend but perhaps now would be a better time with more eyes on it. I was hoping that uuid
might be made to be idempotent. Right now it asserts that its argument is a string so that (uuid (uuid "whatever"))
will necessarily throw an exception. I'm combining some datomic maps together with resource ids on them and it would be nice if I could just run update the keys with uuid regardless of whether they are uuid or string already