Can it be due to the fact that, uhm... the subscribe call is commented out? :)

well 😄

no it was not commented out before

I just commented it out to have the checkbox working

I wonder if it's somehow related to the fact that I use r/as-element instead of creating a more standard reagent component, and so it doesn't detect the fact there is a subscription?

we use r/as-element in many places but never with a subscription inside, so I think it's a possible explanation

That's exactly what I was thinking. Seems like a good lead, but I don't have a deep enough knowledge of Reagent to confirm without experimenting. Try to refactor the [ant/checkbox ...] part into its own Reagent component, just so the subscribe call doesn't happen directly in that fn.

ah nice after doing

(defn row-checkbox
  [{:keys [id]}]
  [ant/checkbox
   {:key       id
    :checked   (contains? @(rf/subscribe [::handlers/selected-rows]) id)
    :on-change #(rf/dispatch [::handlers/toggle-row id])}])

I'm not exactly sure why though

thanks @U2FRKM4TW

NP. My guess is that that fn that calls as-element is not called directly during the rendering phase, and so deref'ing the ratom does not register it as a source of updates for the component. Or maybe simply using as-element prevents that registration mechanism from working.

well I'm still using as-element

so your first guess is probably correct

Yeah, but now the subscription is wrapped in another component and not directly in an argument to as-element.

ah yes sure

@U061V0GG2 Can you please share an opinion on the observed behavior? I couldn't find anything in the docs regarding using ratoms in as-element.

Render fn probably wasn't converted to Reagent component by anything, so the ratoms couldn't register change listener. (r/as-component (fn ...)) might have worked.

But not sure where this render property is used

it's documented here https://ant.design/components/table/#Column

but yeah having it as a separate component/function works well already