Clojurians Log v2

@tomi.hukkalainen_slac has joined the channel

Is it a new norm that cljsjs packages won't be providing via the cljsjs namespace, or just an accidental omission? For example https://github.com/cljsjs/packages/commit/c2a1ba6ade80e8be31196716aa0cc5a515e5c4b3#diff-3e9f409c8bd791752004db5bf19a2beaL35 broke old requires.

It is normal for new style packages.

MaterialUI 1 is new package so there shouldn't be lots of old requires around.

It also broke lots of other things because icons are now separate package etc, so I kind of like that old requires broke

It's not so obvious that it's new, since it still has the same name, even if the source is different

For example clojars shows it just as a newer version

But yeah. I'll just have to figure out how to contact the guy who updated cljs-react-material-ui. He updated the deps, without touching the requires 😕

cljs-react-material-ui is neever going to work with material-ui v1

and afaik it is abandoned

I was thinking about trying https://github.com/stephenway/cljs-material-ui

Okay that could work

At the same time, you can mention that the "usage" section about "I recommend adding this at the beginning of core file" is wrong

Is is required because reagent ns (https://github.com/stephenway/cljs-material-ui/blob/master/src/cljs_material_ui/reagent.cljs) is broken and doesn't require the cljsjs namespace

and it might not work in new Cljs/Closure-library

I've lately worked on refactoring projects from cljs-react-material-ui to just directly calling material-ui through JS interop because the wrapper is unncessary

but I don't have any public examples yet

I think I'll have to go the same route

sigh