Enhancement: integration with dev tools about citrus

[roman01la]

@tkachenko1503 Hi. Thanks! Current architecture doesn't provide core capabilities for integrating development tooling, but you can always hook into state atom with add-watch function. This enables watching state changes over time and building time-traveling debugger, but you can't log actual events. This is temporary solution. I'm considering to work on interceptors as in re-frame, which will allow this kind of tooling. But this is future work.

[roman01la]

I'll drop an example later here

[tkachenko1503]

OK! Thanks

[roman01la]

I just published a package with very basic tooling https://clojars.org/org.roman01la/scrum.devtools

It provides console logger and time-traveling UI with state diffs and current state visualization.

Add to project dependencies: [org.roman01la/scrum.devtools "0.1.0-SNAPSHOT"]

In your code, where you create state atom, do the following to setup devtools:

Require [scrum.devtools.logger :as logger] and [scrum.devtools.ui :as dui]

;; this is your app state
(def state (atom {}))

(when ^boolean goog.DEBUG ;; <= only in dev mode
  (logger/attach! state) ;; <= setup logger
  (dui/mount! state (dom/getElement "debug"))) ;; <= mount devtools UI into the DOM

;; setup reconciler, etc.
;; ...

[escherize]

The repo your clojars link points to is gone.

Is the scrum.devtools repo available elsewhere?

[roman01la]

@escherize no, it's not public. TBH there's nothing super exciting, you can easily hook into atom state and log state changes :)