A debugging dashboard for re-frame. Comes with free x-ray glasses. (Previously known as re-frame-trace)
Go to file
Daniel Compton 158b0059c5 Version 0.0.7 2017-04-13 12:03:01 +12:00
.idea Add code style settings 2016-11-06 16:50:03 +13:00
docs/images Add trace window picture 2017-03-28 20:36:45 +13:00
src/day8/re_frame Move preload ns to day8.re-frame.trace.preload 2017-04-13 11:19:55 +12:00
test/day8/re_frame/trace Commit changes 2016-11-15 15:06:10 +13:00
.gitignore Add .gitignore 2016-11-06 16:47:17 +13:00
CHANGELOG.md Add changelog 2017-04-13 12:01:24 +12:00
LICENSE Update license copyright 2016-11-06 16:50:12 +13:00
README.md Move preload ns to day8.re-frame.trace.preload 2017-04-13 11:19:55 +12:00
project.clj Version 0.0.7 2017-04-13 12:03:01 +12:00

README.md

re-frame-trace

A trace window for re-frame

Motivation

re-frame provides a data driven architecture, but we need to be able to inspect it. re-frame-trace takes inspiration from redux-devtools, and provides several ways to visualise the structure and state of your re-frame application.

How does it work?

re-frame has instrumentation to collect traces throughout various important points in the lifecycle of a re-frame app. re-frame-trace is a consumer of these traces, and provides visualisations of the traces. These traces have a well-defined structure, and will eventually be standardised, allowing other developers to create their own tooling to work against the traces. Currently, re-frame's tracing and re-frame-trace are in alpha and are subject to change at any time. Caveat usor [sic].

Getting started

There are two requirements to use re-frame-trace:

  1. Compile your app with :closure-defines: "re_frame.trace.trace_enabled_QMARK_" true and :preloads [day8.re-frame.trace.preload], e.g.

    {:builds
       [{:id           "dev"
         :source-paths ["src" "dev"]
         :compiler     {...
                        :closure-defines      {"re_frame.trace.trace_enabled_QMARK_" true}
                        :preloads             [day8.re-frame.trace.preload]}}]}
    

    By default, re-frame tracing is compiled out, so it won't impose a performance cost in production. The trade-off here is that you need to explicitly enable it in development.

    The preloads option (:preloads [day8.re-frame.trace.preload]) has to be set in order to automatically monkeypatch Reagent to add appropriate lifecycle hooks. Yes this is gross, and yes we will try and make a PR to reagent to add proper hooks, once we know exactly what we need.

  2. In your app's view code, add in day8.re-frame.trace/devtools as a sibling to the root application view. For example, if your app looks like this:

    (defn main []
      [re-com/v-box
        ;; your app here
        ])
    
    (defn ^:export start-app
      []
      (myapp.boot/init!)
      (reagent/render (fn [] [main]) (.getElementById js/document "app")))
    

    then you need to modify main to look something like:

    (defn main []
      [:div
        [re-com/v-box
          ;; your app here
          ]
        [trace/devtools]) ;; day8.re-frame.trace is aliased is trace
    

Now you can start up your application. Once it is loaded, press Ctrl+H to slide open the trace panel and enable tracing. When the panel is closed, tracing is disabled.