Fork me on GitHub
#reagent
<
2018-06-13
>
jthibaudeau13:06:03

I've been playing with with-let and am seeing the warning The same with-let is being used more than once in the same reactive context. can't seem to find any information on what causes this

scknkkrer13:06:37

Ok, here is an another silly question --forgive me Clojurians-- What does “:>” stands for ?

scknkkrer13:06:09

I have see that keyword before an external library object called.

mikerod13:06:40

the whole doc is worth reading though if you are wanting to be sure to understand Reagent/JS interop

👍 1
scknkkrer14:06:14

Thank you @mikerod. You saved my day.

🎉 1
tungsten16:06:57

Will reagent 0.8.1 (non npm-deps) be able to integrate with react es2016 modules generated from babel? Has anyone tried this

justinlee16:06:40

@jamesthibaudeau I’ve never actually seen that, but based on the code, I think that would be caused if a with-let component called itself recursively

jthibaudeau19:06:04

The component isn't calling itself anywhere, it does have a type 3 component as a child, not sure if that would cause the warning. I thought it might be because I was using the component in a partial but that doesn't seem to be the case. It is functioning normally just don't like seeing warnings in the console

justinlee19:06:32

sometimes the answer is not to use higher-order-components and just use functions. some of the javascript solutions that use components can be eliminated by the fact that you can manipulate hiccup as data before it is ever turns into a component

👍 1