This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-29
Channels
- # aleph (3)
- # announcements (16)
- # beginners (85)
- # calva (2)
- # cider (13)
- # clj-kondo (84)
- # cljdoc (3)
- # clojure (109)
- # clojure-belgium (1)
- # clojure-china (39)
- # clojure-europe (4)
- # clojure-france (1)
- # clojure-italy (70)
- # clojure-nl (8)
- # clojure-spec (8)
- # clojure-uk (53)
- # clojuredesign-podcast (14)
- # clojurescript (43)
- # cursive (25)
- # data-science (1)
- # datomic (4)
- # emacs (10)
- # figwheel (4)
- # garden (4)
- # graphql (5)
- # jackdaw (10)
- # jobs (5)
- # jobs-discuss (5)
- # lambdaisland (2)
- # leiningen (3)
- # luminus (7)
- # off-topic (32)
- # pathom (11)
- # pedestal (2)
- # planck (15)
- # re-frame (12)
- # reagent (4)
- # remote-jobs (2)
- # shadow-cljs (51)
- # sql (29)
- # tools-deps (47)
oh it is?!
I thought :closure-warnings
was a thing
but not warnings
interesting how that doesn’t let you treat some warnings as errors
seems like a useful feature that could even be implemented upstream
yeah :compiler-options {:warnings {:undeclared-var false}}
would disable that warning
currently it is just a boolean but adding :error
to throw instead of warning would be pretty straightforward. just not sure if it breaks other places that only expect a boolean
when i add something like {:closure-defines {my-app/FOO true}}
, then try to use it somewhere, the compiler returns: Use of undeclared Var my-app/FOO
Do you know some of clojurescript cljs.test pretty printer with colorful expected
actual
structures which works seamlessly with shadow-cljs
?
@karol.wojcik I do not but let me know if you find one
@thheller Maybe you have some ideas how to integrate any of javascript frameworks with clojurescript? I'm trying to find a one which allows to call the test by it's name, because I doubt it can work another way.
shadow-cljs - config: /Users/victor/Ericsson/code/cenx/apps/frontend/eric-cenx-ui/shadow-cljs.edn cli version: 2.8.41 node: v12.7.0
Execution error - invalid arguments to shadow.cljs.devtools.api/loading at (api.clj:1)
{:dev {:target :browser
:output-dir "resources/public/js/compiled/"
:asset-path "/js/compiled"
:modules {:app {:entries [epiphany.core]}}}}
I just got an error that I found a bit bizarre, this is what I see:
------ ERROR -------------------------------------------------------------------
File: /.../common/ui/layout.cljs:572:26
--------------------------------------------------------------------------------
569 |
570 | (def css-button
571 | {:background-color "transparent"
572 | :border "1px solid #c49dc9"
--------------------------------^-----------------------------------------------
.../common/ui/layout.cljs [line 572, col 26] Invalid number: 1px.
does that makes sense to anyone?
@wilkerlucio verify that "
is actually "
. I seen all sorts of weird stuff when copying "
from skype or some other office crap
yes, and that line wasn't changed on my branch
but still causing the build to fail somehow
ouch, I maybe have found it
no, still not working, that was other string changed, but still a valid "
@kasuko I'm guessing this is some sort of dependency conflict. make sure you have the "correct" core.async versions and so on
Yep that was exactly it. I am converting an old project from leiningen to shadow-cljs and it had an old version of core.async
and works on my machine, but not on ci -.-
ok, I'll keep debugging, that was some github merged suggestions, may have to do with it
Yep that was exactly it. I am converting an old project from leiningen to shadow-cljs and it had an old version of core.async
not really any other ideas. the error you get is directly from tools.reader so before any analysis/compilation happens
yeah, was something weird, after I pull and push it got back working :man-shrugging: