I'm using reagent with apollo and I'm using mainly higher order components to inject query results into my components. Basically, it looks like this:

(-> add-activity-button
               reagent/reactify-component
               ((query/all-activities-hoc))
               reagent/adapt-react-class)]])

However, the add-activity-button needs to get other data as well... what would be the best way to pass other arguments to the add-activity-button component?

The function looks like this: (defn add-activity-button [{:keys [day all-activities]}] ...

(so, I need to pass day as well)

@kurt-o-sys I’m not sure how the hoc works, but either the hoc has a mechanism where it passes unknown props or you’ll need to create a factory

ok, I was just hoping I could make something funky with reagent/adapt-react-class or reagent/create-element, but neither seem to work fine 😛

I don’t think so. The issue is that (query/all-activities-hoc) controls the creation of add-activity-button

right. agreed.

so that hoc either has a way to pass through props or you’ll have to preload

oh well, it's actually not that difficult to do it otherwise:

(defn add-activity-button [{:keys all-activities}]
  (fn [day] ...))

that's good enough 😛

or so I thought, I still seem to be missing something...

will do it another way. thx.

this is why we ended up wrapping apollo-client to produce a ratom, instead of using the react-apollo integration

it was too hard to use the HOC / child-as-fn pattern with reagent