There's a 'base_url' in ring if you're using that

does clojure have a tool that does something like this: input: here's a bunch of code here's a bunch of tests output: give me a list of sexps in the code that were NOT executed when all the tests have been run

https://github.com/cloverage/cloverage

anyone familiar with how this black magic: https://github.com/klutometis/reader-macros works ?

How do I set a breakpoint in cloverage to debug how it fails to instrument a piece of code?

(def _1 20) <-- is this asking for trouble? I'm doing some pattern matching work, so I'm thinking of naming some pattern vars _1 2 3 ...

I am not aware of any parts of Clojure that would break because of using names for Vars like that.

You might confuse some readers of the code.

You are on the right side of the official docs for symbol names with such names: https://clojure.org/reference/reader#_symbols

The symbol by itself is by convention_ only used for Vars or locally bound names (e.g. in let/loop binding forms) that will not be used in the body.

I mean to start that last sentence with "The symbol '_' by itself", but my Slack special formatting-fu is weak.

Great; thanks, I think I will be okay, as I tend to use 1 2 only "pre macro expansion", in that I have these rewrite rules defined as: (add 1 2) -> (+ (eval context 1) (eval context 2)) then this "rule" gets translated into a sexp with destructuring , let, <-- and symbols in this form are all gensymmed, so there's no actual 1 2 n the 'post macro' final code

I have an array of maps. I want to update one of the maps by matching on one of its properties. This (for [x arr] (if (== (:id x) 21) (assoc x :name "new") x)) works, but is there a more idiomatic way. Something like a assoc where the match is an arbitrary predicate?

@lee.justin.m Specter is your friend for these things:

user=> (def a [{:name "foo" :id 1} {:name "bar" :id 2}])
#'user/a
user=> (transform [ALL (selected? :id (pred= 2))] #(assoc % :name "not-foo") a)
[{:id 1 :name "foo"} {:id 2 :name "not-foo"}]

I'm trying to learn clojure spec from the offical site, but I don't understand the instrument and check. Does it replace testing? Should I count on random generation for production testing? When should I use it and what functions should I spec?

How can I create a var from a string, e.g. like (var (symbol "bidi.bidi/match-route")) (this doesn’t work)

intern

I'm trying to spec a configuration function. The function input is env vars (map of keyword to string), and return the port as an int. How should I write the s/def for the key port, once for string and once for int?

(def port-regex #"\d+")
(s/def ::port (s/and string? (partial re-matches port-regex)))
(s/def ?port? int?)
(s/def ::config (s/keys :req-un [::port]))
(s/def ::parsed-config (s/keys :req-un [?port?]))

anyone using autoformatters or similar tools has recently had as-> receiving a different indentation style? we haven't updated cljfmt or such. dunno where the change comes from

After setting a function spec, where should I validate it? Should I use conform in the beginning and throw in case of an :invalid?

@itaied you can use the clojure.spec.test.alpha namespace https://clojure.org/guides/spec#_testing

Anyone know what the :v :d :a scores mean in the following library? https://github.com/damionjunk/sentimental

;; Compute the EN ANEW for the provided phrase
(anew/score-phrase "I really love my dog." :english)
;; => {:words ["love" "dog"],
;;     :score {:v 8.145000219345093, :d 6.680000066757202, :a 6.1000001430511475}}

@josh_tackett from the paper cited in the readme: valence, arousal and dominance

@schmee @lee.justin.m a cleaner way to do it with specter: (setval [ALL #(= (:id %) 2) :name] "not-foo" a)

Any ideas how to debug why clojure.tools.namespace/refresh fails with “namespace … not found, compiling:(dev.clj:1:1)“? I’ve got no AOT compilation settings or anything that should intervene with the reload but still it does not work

The class is loaded properly the first time I enter the REPL

in the dev.clj file

@schmee Do you know a good clojure sentiment library?

looks like https://github.com/damionjunk/sentimental is in SNAPSHOT

@josh_tackett no idea, sorry

Ah, it seems that the namespace fails to reload because of something in its contents. I replaced it with just an empty ns declaration and now it refreshed properly

@fmind isn't that for testing? I meant to ask about runtime validations, reject and accept requests according to the spec

1. I realize that most functions should be pure. 2. Occasionally, we write functions f, where the idea is that (f 3 g) means that w emake galls (g 0) (g 1) (g 2), in that order, for its side effects. 3. What is a good way to unit f via clojure.test ?

g is passed in as an arg to f?

yes, g is passed as an arg to f,

We do that by passing in a 'test' implementation of g that does a (swap! expected-g-calls conj params-to-g), where expected-g-calls is (atom [])

Then once f has returned we check that expected-g-calls contains the stuff we thought it should, in the order we thought it should

We tend to do the functional core/imperative shell split, and anything that's going to require with-redefs to test and can't be refactored for that not to be the case goes in the shell

in particular, let's say we want to unit test a function:

(defn f [n g]
  (doseq [i (range n)] (g i)))

@carr0t: yeah, most of the time, we try to split pure/imperative too; in this particular case, we're building a "distributed object", so we're trying to test things like: when an update is called on this obj, these registered handlers fire off ...

boot.user=> (require '[clojure.test :refer :all])
nil
boot.user=> (defn f [n g]
       #_=>   (doseq [i (range n)] (g i)))
#'boot.user/f
boot.user=> (let [g-calls (atom [])
       #_=>       g (fn [i] (swap! g-calls conj i))]
       #_=>   (f 3 g)
       #_=>   (is (= [0 1 2] @g-calls)))
true

1. this is slightly less elegant/verbose compared to previous uses of (ct/is (= ...lhs... ...rhs...)) 2. I don't think one can make it more elegant/concise

@schmee @nathanmarz Thanks for the tips. specter is the boss and is just what I need.

I find exception handling inside of let bindings a bit awkward, and I ran into this try-let project looking for answers. It doesn't really seem like people use it much, so I'm wondering if anyone here has thoughts on alternative ways to address these issues in the motivation section: https://github.com/rufoa/try-let#motivation?

@bj i usually catch within the bindings and bind a value to the symbol that captures the failure and check for it in the body

If you were going to add automated acceptance tests to a full stack Clojure(Script) project today, what would you use?

I’ve used clj-webdriver before with mixed results. Is there anything else I should look at?

I'd write most of my code as *.cljc, and keep only the DOM portion in cljs

@danielglauser https://github.com/igrishaev/etaoin

i’ve also used https://github.com/Mayvenn/limo

Does anyone know of any whitespace-aware Clojure parsers or approaches to build such?

I haven't used it, and I think even the author may anti-recommend it, but sjacket is in that category of tools: https://github.com/cgrand/sjacket I do not know the reasons it may be anti-recommended, if it is.