Yep.

@madvas I'm trying to use cljs-react-material-ui package and I keep running into the react included twice problem in advanced optimization mode. As far as I can see it's required once in my core file and react should not be depended twice in the project. Do you have any tips on how to debug this issue?

I noticed there was an issue about this in the repo and various references to found while googling but no definite solution

any recommendations for doing currency arithmetic on the client? the computed values aren’t just for display; they’ll get saved. Typically, I’d just do this on the server, but curious if the alternative is viable.

can anybody help me how to fetch from clojurescript in a reagent environment a remote json and display it?

Sometimes I don’t get an error message when I move a namespace to some other directory, because the structure and namespace name don’t match, but my app doesn’t work anymore. Is this a known issue? I’d rather have an error message by the compiler. This is only when incrementally compiling.

@borkdude tools.namespace/refresh destroys namespaces before reloading code, and thus would make this show up as an error immediately

tools.namespace doesn't really work with Cljs 😉

ugh! I keep forgetting which channel I’m in, sorry

One thing that might affect this is that Cljs compiler doesn't remove removed files from compiler cache

https://clojurians.slack.com/archives/C03S1L9DN/p1515097965000414

Though, in that case the app would be working, as it would still use the old namespace. More specific test case would help on understanding what happens.

I notice I can reproduce it on first compilation by using the wrong namespace name in a file, e.g. /src/foo/bar.cljs with (ns foo.bar2) instead of (ns foo.bar). It won’t produce an error but causes unexpected behavior. I’ll have to test this in a mini project

@borkdude one problem is that ClojureScript was originally file system oriented

you compiled a source directory and structure of what was in there didn’t matter

but you also have cases where it’s not going to match

Google Closure style JS libs, ES6 stuff

one thing worth mulling over is whether should be some kind of strict mode where ns names of CLJS sources must always be correct with respect to file system location

Yeah, or at least a warning from the compiler if it detects an inconsistency with cljs file structure?

we do warn of course

just not for stuff directly under src

the directory you want to compile

one way to avoid this is always use :main

so you’re not compiling random stuff, but only things reachable via require

and then you’ll get all the warnings you want

unless you name :main itself badly

@borkdude oh that’s a different problem than what I expected

if the file is in the write place with the wrong namespace

open a JIRA ticket for that please

@dnolen https://dev.clojure.org/jira/browse/CLJS-2459

I could not select version 1.9.946 in Jira, so I selected the latest I could find