This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-28
Channels
- # arachne (2)
- # aws (5)
- # aws-lambda (5)
- # beginners (4)
- # boot (25)
- # cljs-dev (270)
- # cljsjs (1)
- # cljsrn (72)
- # clojars (5)
- # clojure (201)
- # clojure-belgium (5)
- # clojure-brasil (4)
- # clojure-italy (2)
- # clojure-korea (2)
- # clojure-russia (24)
- # clojure-spec (24)
- # clojure-uk (22)
- # clojurebridge (1)
- # clojurescript (125)
- # cloverage (3)
- # cursive (41)
- # datomic (37)
- # dirac (4)
- # emacs (2)
- # hoplon (421)
- # lein-figwheel (1)
- # leiningen (5)
- # luminus (2)
- # mount (1)
- # off-topic (18)
- # om (44)
- # om-next (4)
- # onyx (44)
- # pedestal (3)
- # proton (9)
- # re-frame (21)
- # reagent (21)
- # ring-swagger (12)
- # specter (9)
- # sql (2)
- # untangled (62)
- # vim (16)
god morgen
anyone played with clojure slack bots? There seem to be a few slack libraries out there, and a few bots, but the bots seem to be a bit alpha-quality (and don’t use the libraries!)
… and the libraries don’t give examples. I’m lazy, dammit, I just want to steal code that lets me write a bot quickly! 🙂
i’ve done them with node in the past using the official slack npm package - dunno if the JVM one is any good, but CLJS might work fairly quickly
I saw a london clojure talk on a pedestal based slack bot, looked interesting. I started with a plan to make one using that ring lambda lib, got as far as hello worlding an endpoint I think
@korny you can either look at that one for a web hook based approach (request/response behaviour) or there is a channel based approach where you listen to every message
That was the initial spike using the channel approach but the request/response idiom was better