This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-20
Channels
- # announcements (27)
- # aws (1)
- # beginners (62)
- # boot (5)
- # calva (56)
- # clj-kondo (6)
- # cljdoc (3)
- # cljsrn (4)
- # clojure (65)
- # clojure-dev (17)
- # clojure-europe (2)
- # clojure-italy (17)
- # clojure-nl (24)
- # clojure-spec (30)
- # clojure-uk (14)
- # clojurescript (35)
- # clr (7)
- # cursive (8)
- # data-science (3)
- # datascript (38)
- # datomic (15)
- # emacs (16)
- # fulcro (34)
- # hyperfiddle (1)
- # immutant (1)
- # luminus (7)
- # nrepl (1)
- # off-topic (38)
- # pedestal (2)
- # planck (10)
- # re-frame (7)
- # reagent (7)
- # reitit (9)
- # shadow-cljs (36)
- # sql (19)
- # tools-deps (11)
- # vim (64)
- # xtdb (18)
@thheller sorry, bad example. Toolbar is a part of ["@material-ui/core/Toolbar" :default tool-bar]
. I installed material-ui with npm and got it working. The other material ui components that I require looks like this #Object[WithStyles]
but Toolbar is just empty #js {}
.
I have a script in CircleCI to deploy my webapp. But sometime app.js fails to generate and it doesn't get uploaded. Any ideas of what could cause that?
I'm generating and deploying two seperate shadow-cljs projects with different shadow-cljs.edn
files with shadow-cljs release app
. They are run one after the other too
@jarvinenemil see the documentation about :default
, you should probably try :as tool-bar
instead. :default
is currently in a weird situation. https://shadow-cljs.github.io/docs/UsersGuide.html#_about_default_exports
thanks, ill try it out. will report back. I am planning on putting together a repository showcasing how to use material ui with shadow-cljs, (app-bar, etc..) đ
a bit wierd that i tried both before though, but ill have a look once i get home
It works now, I think it was some NPM issues.
I have to improve my bug search skills though
@caleb.macdonaldblack CircleCI is notorious for killing build processes for consuming too much memory. so the OOM killer just hard terminates the process and pretends that everything is fine.
@thheller So it will kill a process for a command in my bash script and continue with the remaining commands like normal?
Wow, thanks. If that works I never would've figured that out on my own.
I just got material ui working, then I restarted my repl and it stopped working. Anyone has any ideas? Or have also had problems with material ui with shadow?
(:require
["@material-ui/core" :as mui]))
(defn header []
[:> mui/AppBar {:position "static"
:color "primary"
:style {:background-color "#43a047"}}
[:> mui/Toolbar
[:> mui/Typography {:variant "h6"
:color "inherit"}
"BH"]
[:> mui/Button {:color "inherit"} "Login"]]])
(defn app []
[:div
[header]])
I havenât had any issues so far, my imports are structured like
["@material-ui/core/Button" :default button]
["@material-ui/core/Switch" :default switch]
["@material-ui/core/Textfield" :default textfield]
["@material-ui/core/FormControl" :default form-control]
["@material-ui/core/FormControlLabel" :default form-control-label]
["@material-ui/core/InputLabel" :default input-label]
["@material-ui/core/Typography" :default typography]
["@material-ui/core/Select" :default select]
["@material-ui/core/MenuItem" :default menu-item]
["@material-ui/core/Dialog" :default dialog]
["@material-ui/core/DialogTitle" :default dialog-title]
["@material-ui/core/Paper" :default paper]
["@material-ui/core/styles" :rename {withStyles with-styles}]
["@material-ui/icons/Add" :default add]
this is the error i keep on getting
Looks like some hot reloading issue?
@U9MJTSS9K which version of material-ui are you on?
hmm.. same here, wierd.
in the chrome tools it warns: it fails to load the material ui components e.g module$node_modules$$material_ui$core$Paper$Paper
(:require
["@material-ui/core/AppBar" :default app-bar]
["@material-ui/core/Toolbar" :default tool-bar]
["@material-ui/core/Button" :default button]
["@material-ui/core/Typography" :default typography]
["@material-ui/core/Menu" :default menu]
[reagent.core :as r]))
(defn header []
[:> app-bar {:position "static"
:color "primary"}
[:> tool-bar
[:> typography {:variant "h6"
:color "inherit"}
"App-Title"]]])
(defn app []
[:div
[header]])
updated to thisdoes not help đ same error
it fails to load the node modules somehow
Now it works again.
ran: npm dedupe npm ls and added (to shadow-cljs.edn):
[com.google.javascript/closure-compiler-unshaded "v20190325"]
[org.clojure/google-closure-library "0.0-20190213-2033d5d9"]
đ ...I have a very small shadow-cljs app running, connected to REPL w/ Emacs. I have a core.async go-loop that starts up and parks waiting for input from a channel. What happens to the go-loop when I 1) hit Save in the editor, does that original go-loop keep running? Does an additional go-loop get created each time I hit Save? Do I need to add some kind of lazy-init/singleton/safeguard logic to ensure the go-loop is only created once? Is there a recommended pattern to follow? And then 2) same questions, except for hitting Reload in the browser (rather than Saving sourcecode)