This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-24
Channels
- # adventofcode (11)
- # architecture (12)
- # beginners (132)
- # boot (19)
- # cider (26)
- # clojure (69)
- # clojure-dusseldorf (4)
- # clojure-gamedev (1)
- # clojure-italy (46)
- # clojure-nl (4)
- # clojure-serbia (1)
- # clojure-switzerland (2)
- # clojure-uk (91)
- # clojurescript (79)
- # css (4)
- # cursive (2)
- # datomic (16)
- # docs (9)
- # duct (20)
- # editors (94)
- # fulcro (15)
- # graphql (2)
- # hoplon (1)
- # instaparse (7)
- # jobs (3)
- # lein-figwheel (3)
- # leiningen (2)
- # lumo (40)
- # mount (35)
- # off-topic (19)
- # reagent (18)
- # reitit (1)
- # shadow-cljs (123)
- # specter (7)
- # sql (5)
- # test-check (4)
- # tools-deps (38)
- # vim (20)
- # yada (9)
@bhauman (using figwheel-sidecar) I've recently gotten hung up on some bugs that caused warnings in one of my namespaces. If I run a (reset-autobuild) I see the warnings. If I call (build-once) the warnings don't show up in either REPL or console. Is this expected? When these warnings are thrown, I get 'Cannot read property 'call' of undefined errors' from the offending namespace.
@jrbrodie77 so yes this is expected behavior, a complete build will compile everything and thus pick up any warning that may exist in the code. But you can get a warning, and miss it, and then move to work another file and everything will seem like its fine.