This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-21
Channels
- # architecture (9)
- # beginners (192)
- # boot (1)
- # bristol-clojurians (2)
- # cider (213)
- # cljs-dev (10)
- # clojure (195)
- # clojure-art (2)
- # clojure-austin (3)
- # clojure-belgium (4)
- # clojure-dev (4)
- # clojure-dusseldorf (1)
- # clojure-gamedev (9)
- # clojure-greece (21)
- # clojure-italy (27)
- # clojure-losangeles (2)
- # clojure-russia (1)
- # clojure-seattle-old (2)
- # clojure-serbia (1)
- # clojure-spec (114)
- # clojure-uk (136)
- # clojured (2)
- # clojurescript (100)
- # community-development (19)
- # core-async (12)
- # cursive (7)
- # duct (1)
- # figwheel (7)
- # fulcro (96)
- # hoplon (4)
- # jobs (2)
- # lein-figwheel (28)
- # leiningen (2)
- # luminus (14)
- # lumo (3)
- # off-topic (11)
- # om-next (2)
- # pedestal (10)
- # planck (11)
- # portkey (2)
- # proton (1)
- # protorepl (19)
- # re-frame (27)
- # reagent (12)
- # shadow-cljs (82)
- # spacemacs (42)
- # specter (15)
- # sql (3)
hey react users, @mikethompson, @mikerod (and any other mikes of the world), I finally pulled together most of the documentation from /docs and from the release notes into a single markdown file. I have also added my own React interop guide. For now, I just put the draft up here https://gist.github.com/jmlsf/17c588deb326e538dcea6847bc66db9b but I’d appreciate thoughts on how best to finish this up and share it. I have read through https://github.com/reagent-project/reagent/issues/209 and realize there are a lot of opinions on doc technology, but I think the advice to just get the content done in the easiest way possible is well taken. Is a pull request the right thing to do here? I want people to be able to contribute easily. There are quite a few TODOs in places where my knowledge is missing.
@lee.justin.m I think there are good comments on the PR 343 at this point from those who have more to say regarding organization and process.
I read the section that I believe that you added on “Interop with React” and I think it was well said and captures what I think would be helpful to people there. So I don’t have anything to add other than +1 to that section. I’ll keep an eye on the Reagent docs overall and that PR to see how things go from here.
@lee.justin.m Woohoo, this is exciting! Yes, I think a PR is the right thing to do here
@lee.justin.m If you haven't seen it, 302 (https://github.com/reagent-project/reagent/issues/302) is also a relevant issue along with 209 which you already referenced
@lee.justin.m sent over a PR to your version ... just adding tags to a few missed source code blocks