This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-10
Channels
- # announcements (6)
- # architecture (2)
- # babashka (30)
- # beginners (90)
- # calva (21)
- # cider (22)
- # clj-kondo (27)
- # cljs-dev (7)
- # clojure (132)
- # clojure-europe (51)
- # clojure-nl (12)
- # clojure-norway (3)
- # clojure-spec (3)
- # clojure-uk (5)
- # clojurescript (69)
- # cloverage (9)
- # conjure (5)
- # core-async (54)
- # cursive (14)
- # datomic (34)
- # emacs (7)
- # fulcro (10)
- # graalvm (40)
- # graalvm-mobile (2)
- # gratitude (2)
- # improve-getting-started (1)
- # introduce-yourself (1)
- # jobs-discuss (61)
- # leiningen (5)
- # malli (6)
- # off-topic (59)
- # pathom (11)
- # polylith (38)
- # reagent (3)
- # reitit (3)
- # rewrite-clj (3)
- # shadow-cljs (53)
- # tools-build (35)
- # transit (8)
- # vim (62)
- # web-security (26)
- # xtdb (4)
How do you usually do code reviews? Github has this view where you can add comments/suggest changes to specific parts of a PR and I've been wondering if anyone has managed to make emacs integrate well with it? I'd love to have that on top of paredit, clojure-mode and cider.
I remember a peer using what I think was https://github.com/wandersoncferreira/code-review ? cc/ @UBSREKQ5Q who authored the package in question!
🙏 2
Thanks, I'll check it out! Code reviews is the part of development that I spent the most outside of my comfort zone emacs and I don't like it 😛
😇 1
🎉 1
Feel free to send some feedbacks after you try the package 🙂 always good to hear users feedback
👍 1