Fork me on GitHub
#reagent
<
2019-01-25
>
WhoNeedszZz04:01:39

I figured out it was just IE/Edge not supporting :flex-direction "column"

😱 1
valtteri08:01:36

One of the upsides of widely user react libs is that there’s usually a large amount of crazy enough contributors to hunt down and fix the browser compatiblity issues. Downside is that the libs often turn out too bloated because of myriads of edge-cases (heh) and contributors.

valtteri08:01:12

I try to avoid features that are known to be difficult for IE11 and Edge. https://caniuse.com/ is a good resource.

👍 1
valtteri08:01:45

It also depends on your audience. In my case I was a bit surprised that 25% of visitors use IE11 or Edge. Our users are mostly working in governmental / municipal agencies where IT-departments seem to favour legacy crap. If the percentage was around 5% I wouldn’t care that much.

Whiskas14:01:46

There is any good Material-ui Reagent Wrapper out there which is compatible with the latest version of material-ui?

valtteri14:01:55

@mateus.pimentel.w you don’t need wrapper. Reagent repo has example project how to use Material-ui “directly” via interop https://github.com/reagent-project/reagent/tree/master/examples/material-ui

valtteri14:01:00

Best way to get the latest version is to get it from npm and use webpack or shadow-cljs to bundle it into your build.

valtteri14:01:16

No problem!

exit216:01:58

Is there a way, by updating app-state that you can force your initial API calls to trigger again? If I call the fetch function directly it causes the page to flash

lilactown17:01:29

@njj that sounds weird. why is it flashing?

exit217:01:18

heh thats what I’m trying to figure out

exit217:01:51

it maybe my setup, I’m trying to console the app state from the init! function and it’s not printing anything on updates, but higher up in the components things update