This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-10
Channels
- # admin-announcements (1)
- # aleph (1)
- # asami (9)
- # babashka (30)
- # beginners (83)
- # calva (8)
- # cherry (4)
- # cider (4)
- # clj-kondo (15)
- # cljs-dev (11)
- # cljsrn (8)
- # clojure (85)
- # clojure-europe (87)
- # clojure-losangeles (9)
- # clojure-nl (4)
- # clojure-norway (4)
- # clojure-spec (3)
- # clojurescript (12)
- # community-development (5)
- # conjure (1)
- # core-typed (3)
- # datomic (21)
- # docker (13)
- # emacs (13)
- # funcool (1)
- # google-cloud (1)
- # graalvm (12)
- # gratitude (14)
- # holy-lambda (6)
- # introduce-yourself (18)
- # lsp (15)
- # malli (6)
- # matcher-combinators (15)
- # nbb (15)
- # off-topic (37)
- # pathom (31)
- # portal (23)
- # rdf (3)
- # releases (2)
- # reveal (2)
- # sci (4)
- # scittle (3)
- # shadow-cljs (14)
- # squint (2)
- # tools-deps (29)
Hello! First time interop'ing with js in cljs, I installed this qrcode library: https://github.com/soldair/node-qrcode with npm. I then did add it to my :require list as:
(:require
["qrcode" :as qr]))
Adding (qr/toDataURL "hello there" #(println "CALLBACK" %))
somewhere, lead to CALLBACK nil
in the console
Any ideas?QRCode.toDataURL('I am a pony!', function (err, url) {
console.log(url)
})
looks like it's working try replacing %
with %2
to get the urlThat would be %&
. :) But it would also be nil
if there are no arguments passed to such a lambda.
With that being said, if a lambda takes more than one argument, you should probably avoid the #(...)
shortcut and instead use (fn [...] ...)
.
Hi all! I'm trying to use jest for testing my (react-based) clojurescript web app. I've got it mostly working, except for one thing: rerunning tests on changes. Jest determines changes based on git status, but in my case the test files are the files that are output by the compiler (shadow-cljs), hence they are in my gitignore and jest says that nothing has changed. So it's basically all or nothing: always rerun all tests (impractical) or it thinks there is nothing to run. Does anybody know of a solution to this problem? (@pesterhazymaybe? https://clojurians.slack.com/archives/C03S1L9DN/p1629265015441200?thread_ts=1629215985.430500&cid=C03S1L9DN) Thanks!
I don't know a solution to the problem unfortunately
If jest were able to rerun based on timestamp, that would work
The whole setup of watching a folder containing build artifacts strikes me as brittle
But not sure how to fix it without writing your own test runner
Did you have any insights in the meantime?