The need to potentially start porting an existing app to start using a clojurescript core

r/atoms won't really work in the same way.

they work with the "reagent render loop" where you produce hiccup and then convert that to react at the very end - if you got a handle to a reagent atom in a normal react component it wouldn't work

what you can do is pass the current value and a function that will swap the current value down

so

Hmmm, because I was looking into replacing recoil which basically works like atoms but in a react setting

https://recoiljs.org

function YourReactComponent({ value, swapValue }) {
   <button onClick={() => { swapValue(v => v + 1); }> {value} </button>
}

(defn your-reagent-component 
  []
  (let [value-atom (r/atom 0)]
    [:> YourReactComponent {:value @value-atom :swapValue #(swap! value-atom %)}]))

I see, not the path of replacement i was thinking of, which was to make a clojurescript library imported into the javascript code

Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

As I mentioned in the other channel - it's probably an incorrect import.

What's exactly in your :require?

Yes, but I can get the object out of the js console

["primereact/button" :refer (button)]

Then in browser console I can see the object in module$node_modules$primereact$button$button_cjs

A side-note using parentheses instead of brackets in the :require vector is generally discouraged. But it's not that important. If (js/console.log button) does log a button component then that error comes from some different place, because it's about undefined .

Alternatively, that button component itself requires some argument that has to provide a string/class/function. But that argument is not checked explicitly in button, and you don't provide the value.

Yeah, I might just give up and use @material-ui because that road is paved haha

You mean, you have used MUI before and are aware of all its quirks?

Because if not, MUI has definitely quirks on its own that you might encounter sooner or later.

I've used it in angular, so if they are the design system quirks I've probably hit them all

if there are implementation quirks no, but at least I can find some sample code

Holy crap I see a button

There's still the interop friction, that sometimes can be more than one would like.

Good. :)

the props aren't there but its a start! 🙂

THanks for your patience!

@U2FRKM4TW you've created a monster, already wrapped a few of the PrimeReact components in nicer cljs fns and added some icons from another react component library altogether 🙂

Keep that excitement up! :D

That's really easy to do -- once you get past the gap between the code and the browser.. but it's not really any better/worse than webpack / typescript etc 😄

In my experience, it's absolutely better. Much so. The code reloading itself is insanely good. Implementing undo/redo mechanism is easy when you have immutable data everywhere. And many other nice things that come from Clojure being a LISP.