Clojurians
#reagent
<
2016-09-28
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

royalaid00:09:57

Quick question, how can I add the autoplay attr to a video in reagent? I have tried {:autoPlay ""} {:autoplay "autoplay"} {:autoplay ""}

royalaid00:09:39

and obviously I can't just {:autoplay}

michael.heuberger00:09:02

tried with {:autoplay true} yet?

metametadata07:09:26

@johanatan I doubt such tool can be implemented to work with any kind of ClojureScript or even Reagent app. The time travelling debugging as demonstrated in Elm (and also ReduxJS and Carry which were inspired by Elm architecture) requires the app to be structured in very specific way - single store, explicit events/actions/what-you-name-it, clear separation of actions which have side-effects (and thus should not be replayed), etc. Re-frame probably may support this kind of debugging, especially with the recent additions of "effects", but I don't know if there's any such project around.

reefersleep11:09:39

@metametadata @johanatan: I don't think that a project exists, but I suspect people may be working on it. It seems like low-hanging fruit. I'm contemplating putting something together myself :slightly_smiling_face:

reefersleep11:09:45

But it requires you to do a bit more than just use re-frame - you need to wrap the dispatch fn so you can log all events and app-db snapshots.

reefersleep11:09:46

According to @mikethompson, this is good practice, though, as having your own wrapper around dispatch also allows you to do a lot of stuff by inserting app-wide interceptors that affect each dispatch call.

reefersleep11:09:58

Such as logging or whatever.

kauko13:09:29

You shouldn't need to store app-db snapshots though. Just nitpicking :stuck_out_tongue:

galvs14:09:35

Anyone got any tips for using semantic ui's sidebar? got it working but with warnings about not being a child of 'body'

gadfly36114:09:23

@galvs ive only got it working by making a second target div in index.html

samueldev14:09:42

When my browser auto-fills an input (saved un/pw for example), it isn't triggering the on-change of my component, seems like this is just known behaviour in many browsers, wondering if there's any good re-frame/reagent workaround

gadfly36114:09:43

Sibling to app

johanatan15:09:25

@metametadata: yes, as @reefersleep mentioned, re-frame does actually support that architecture as of 0.8.0 (with the addition of fx)

johanatan15:09:01

@reefersleep: awesome, will be great to see what ppl come up with !

novakboskov16:09:24

Does anyone here have experience with react-select?

eyelidlessness19:09:03

(defn some-component [& args]
  (reagent/create-class
    {:component-did-mount (fn [component] (println (reagent/argv component)))
     :reagent-render (fn [& args] [:div])}))

[some-component :a :b :c] ;; Once mounted, prints (some-component :a :b :c)

(def partial-component (partial some-component :a))

[partial-component :b :c] ;; What is expected to print here?

eyelidlessness19:09:07

i would have expected the same output, but it’s not

gadfly36120:09:44

reagent/create-component --> reagent/create-class