This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-22
Channels
- # announcements (2)
- # aws (5)
- # babashka (17)
- # beginners (108)
- # calva (28)
- # chlorine-clover (7)
- # clj-kondo (14)
- # cljs-dev (9)
- # cljsrn (2)
- # clojure (118)
- # clojure-europe (50)
- # clojure-finland (5)
- # clojure-france (15)
- # clojure-italy (9)
- # clojure-nl (14)
- # clojure-spec (11)
- # clojure-uk (43)
- # clojuredesign-podcast (1)
- # clojurescript (35)
- # clojutre (2)
- # clr (3)
- # community-development (6)
- # conjure (9)
- # core-async (41)
- # cursive (7)
- # data-science (7)
- # datomic (11)
- # events (1)
- # figwheel-main (4)
- # fulcro (20)
- # ghostwheel (9)
- # graalvm (18)
- # helix (46)
- # leiningen (14)
- # observability (2)
- # off-topic (23)
- # pathom (4)
- # re-frame (5)
- # reitit (5)
- # rum (2)
- # shadow-cljs (32)
- # spacemacs (8)
- # specter (5)
- # sql (36)
- # timbre (3)
- # vim (15)
- # xtdb (2)
- # yada (2)
here's a pod to call the peg functionality provided by the janet programming language: https://github.com/sogaiu/pod-janet-peg
🤯 8
Hey don’t know if it’s a feature or a bug but I’ve just realised you can’t have the port in the url (e.g doing curl/get
) as this is going to be ignored given
https://github.com/borkdude/babashka.curl/blob/82a6571d51abee402e0b40be984420000fe1c08b/src/babashka/curl.clj#L252-L257 I think it’d be nice if we could do that (as I was really confused why that wasn’t working - happy to contribute) but understand if the prefered approach is to use curl/request
:thumbsup: