This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-21
Channels
- # 100-days-of-code (1)
- # announcements (2)
- # beginners (164)
- # cider (23)
- # cljs-dev (30)
- # cljsjs (11)
- # cljsrn (7)
- # clojure (116)
- # clojure-boston (1)
- # clojure-dev (20)
- # clojure-finland (2)
- # clojure-italy (4)
- # clojure-nl (1)
- # clojure-uk (10)
- # clojurescript (39)
- # core-async (19)
- # cursive (43)
- # data-science (2)
- # datomic (24)
- # emacs (10)
- # figwheel-main (20)
- # fulcro (63)
- # hoplon (7)
- # hyperfiddle (7)
- # instaparse (3)
- # kaocha (1)
- # nrepl (3)
- # off-topic (170)
- # onyx (13)
- # other-languages (3)
- # parinfer (13)
- # re-frame (39)
- # reagent (5)
- # reitit (22)
- # ring-swagger (4)
- # shadow-cljs (284)
- # spacemacs (2)
- # sql (27)
- # testing (28)
- # unrepl (2)
@miikka Thanks much!!
@jsa-aerial If you have a patch ready to update vega-embed, please submit a PR and let's merge it.
Will do!
OK, done and checks pass. But I see that you went ahead and merged the 3.23.1 - I used my fork as updated to latest CLJSJS before that update, so there are 'conflicts' because the version 3.24.1 is being compared to 3.16.1-1 - same with old vega and vega-lite in build.boot.
OK, in order to prevent this sort of nonsense in the future, I would be willing to be the point person to keep these (the various vega libs) properly updated. I think I saw a place where one can sign up for that but can't find it now. Can you point me to that?
I don't think that I merged any changes to vega-embed? The boot-cljsjs dependency has been updated and that's why there are the conflicts.
Maybe you meant this? https://github.com/cljsjs/packages/blob/master/CODEOWNERS
Yes, that looks like what I meant. So, do I just add stuff to that and give PR for it?
OK, sorry, on conflicts it looked like it was complaining about something else - I must have misunderstood. THANKS for the update!