гм

а что такое did-remount?)

*hm. what is did-remount?

in rum callbacks? I cannot find this calllback in original react

it should’ve been called will-remount

analogous to componentWillReceiveProps

>_< trying to learn both react and rum at the same time) each has its own state, to my understanding >_<

Yes

They are called the same but work differently

what is the main goal of rum state as compared to react state? (I think I'm starting to have more or less of an idea what is react state - it keeps some javascript objects under the hood, applying callbacks during unmounting and remounting components during virtual dom to dom diffing)

(will read rum source in a couple of hours, I guess)

(also are mixins equivalent of wrapping a component with another components? Say, I have 3 mixins = 3 wrappers)

Same, actually: keep track of stuff local to component

stupid question - could react state be used?

Main difference is that Rum state immutable

Sure, (:rum/react-component state) and (.-setState ...) on it

I mean, I'm trying to figure out design goals

hm. need to check the source code)

Mixins are not wrappers, rather, they are lifecycle callbacks

yes, but component can have 4 mixins. I figure, they will be called in an order

Yes

of definition. so can I during compilation rewrite it as an equivalent of 4 wrapping components, that will do the same

Mixins stack on top of each other

(just trying to figure out what do react users use in stead of mixins)

React users use React class

It has same lifecycle callbacks as Rum mixins

Also, they have mixins in React too

oh

So React has two ways to specify lifecycle callbacks, while Rum has only one

(I'm just curious of theorical equivalence)

Simple :)

ok)

can I return my own state in rum did-mount callback, or I should only assoc into it?

it seems that callback state to be getting merged with rum internal state all the time

(rum/defcs odometer < #_(rum/local nil)
  {:did-mount (fn [state] #?(:cljs {:odometer {}}
                            :clj  {:odometer {}}))
   :did-update (fn [state] state)}
  [state value]
  [:div "state is: '" (str state) "' and value is " value])

on mounting it has internal :rum/component, on updating there is no rum/component, however rum/args are still there

ah

I see where to get args now)

from rum/args)

I'll go watch the workshop again.

yes, I was basically erasing rum state, probably

merging with it works just fine

Yeah don't erase rum internal state please

🙂

last question

how do I (you?) debug rum components?

with all that threaded (incapsulated?) state I can't REPL into rum component state

I guess I cannot reuse facebook's chrome plugin

Chrome plugin works, more or less

You'll see ClojureScript maps though

I debug with println