status-im
/
re-frame-10x
mirror of https://github.com/status-im/re-frame-10x.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Rename strings and docs to re-frame-10x 

Namespaces and function names in a later commit.
This commit is contained in:
Daniel Compton 2018-02-20 14:40:17 +13:00
parent 8bba648914
commit 9629ad9dac
26 changed files with 91 additions and 81 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
CHANGELOG.md
View File

@ -1,7 +1,17 @@
# Change Log
All notable changes to this project will be documented in this file. This change log follows the conventions of [keepachangelog.com](http://keepachangelog.com/).
## [0.1.21] - Unreleased
## [0.2.0] - Unreleased
* re-frame-trace has been renamed to re-frame-10x. You will need to update your dependency from `day8.re-frame/trace "0.1.21` to `day8.re-frame/re-frame-10x "0.2.0`
## [0.1.22] - 2018-02-20
### Changed
* This is the final release of this project under the `day8.re-frame/trace` artifact ID. The only change from 0.1.21 is that this version will print a warning to the console every time you load it, reminding you to update to `day8.re-frame/re-frame-10x`.
## [0.1.21] - 2018-02-14
### Fixed

28
DEVELOPERS.md
View File

@ -1,22 +1,22 @@
## Development
### Setting up re-frame-trace for development
### Setting up re-frame-10x for development
You need both the re-frame-trace project _and_ a test project to develop it against. For example, you can use the [todo-mvc](https://github.com/Day8/re-frame/tree/master/examples/todomvc) project.
You need both the re-frame-10x project _and_ a test project to develop it against. For example, you can use the [todo-mvc](https://github.com/Day8/re-frame/tree/master/examples/todomvc) project.
- Clone `re-frame-trace` to your machine:
- Clone `re-frame-10x` to your machine:
```
git clone git@github.com:Day8/re-frame-trace.git
git clone git@github.com:Day8/re-frame-10x.git
```
- Go into the root folder of the test project you're using to develop re-frame-trace with.
- Go into the root folder of the test project you're using to develop re-frame-10x with.
```
cd /your/project/folder
```
- Add re-frame-trace into this test project using the [instructions](README.md#installation) above.
- Add re-frame-10x into this test project using the [instructions](README.md#installation) above.
- Still in the test project, create a folder called `checkouts`, then enter the folder:
@ -25,28 +25,28 @@ You need both the re-frame-trace project _and_ a test project to develop it agai
cd checkouts
```
- Create a [relative symlink](https://superuser.com/questions/146231/how-do-i-create-a-relative-symbolic-link-in-linux) from your local re-frame-trace project in the checkouts folder. For example:
- Create a [relative symlink](https://superuser.com/questions/146231/how-do-i-create-a-relative-symbolic-link-in-linux) from your local re-frame-10x project in the checkouts folder. For example:
```
ln -s ../relative/path/to/your/local/re-frame-trace re-frame-trace
ln -s ../relative/path/to/your/local/re-frame-10x re-frame-10x
```
- If you're using figwheel in the test project, you need to add the checkouts folder (`checkouts/re-frame-trace/src`) to `:cljsbuild :source-paths` in the `project.clj` file. If you're having trouble locating the right place to put this, it might help to look to a sample [project.clj](https://github.com/technomancy/leiningen/blob/stable/sample.project.clj) for inspiration. For example:
- If you're using figwheel in the test project, you need to add the checkouts folder (`checkouts/re-frame-10x/src`) to `:cljsbuild :source-paths` in the `project.clj` file. If you're having trouble locating the right place to put this, it might help to look to a sample [project.clj](https://github.com/technomancy/leiningen/blob/stable/sample.project.clj) for inspiration. For example:
```
:cljsbuild {:builds {:client {:source-paths ["checkouts/re-frame-trace/src"]}}}
:cljsbuild {:builds {:client {:source-paths ["checkouts/re-frame-10x/src"]}}}
```
- re-frame-trace has a debug panel useful when developing it. You can enable it by adding the :closure-define `"day8.re_frame.trace.debug_QMARK_" true` to your compiler settings.
- re-frame-10x has a debug panel useful when developing it. You can enable it by adding the :closure-define `"day8.re_frame.trace.debug_QMARK_" true` to your compiler settings.
- Now run your test project however you usually run it, and re-frame-trace should be in there. \o/
- Now run your test project however you usually run it, and re-frame-10x should be in there. \o/
### Developing CSS
The styles for the trace panel are defined both inline and in Garden styles in `day8.re-frame.trace.styles`.
We are using CSS preprocessing to isolate the panel styles, by namespacing the panel styles with the id `#--re-frame-trace--`.
We are using CSS preprocessing to isolate the panel styles, by namespacing the panel styles with the id `#--re-frame-10x--`.
#### Problems while developing CSS
@ -58,7 +58,7 @@ We want to use re-frame, but we don't want to use the re-frame that the host is
Run `./source-deps.sh` to update the source dependencies.
### How does re-frame-trace build?? I don't see anything in the project.clj that looks like it will build.
### How does re-frame-10x build?? I don't see anything in the project.clj that looks like it will build.
When you add a path to the :source-paths of the test project used to develop the trace panel against, figwheel in the test project will know to watch and build it too.

28
README.md
View File

@ -1,6 +1,6 @@
# re-frame-trace
# re-frame-10x
`re-frame-trace` let's you instrument, and then inspect, the inner workings of a running `re-frame` application. It presents as a programmer's dashboard, delivering curated insight and illumination.
`re-frame-10x` let's you instrument, and then inspect, the inner workings of a running `re-frame` application. It presents as a programmer's dashboard, delivering curated insight and illumination.
### It Is Epoch Oriented
@ -15,12 +15,12 @@ which can be inspected, analysed and understood independently of other epochs. T
tool is epoch-oriented - it shows you one at a time.
And, yes, it has "time travel debugger" capabilities - you can go
[backwards and forwards through epochs](https://condenaststore.com/featured/the-conga-line-of-past-selves-a-string-liana-finck.html) - but that's really not the most interesting or powerful aspect of what `re-frame-trace` delivers.
[backwards and forwards through epochs](https://condenaststore.com/featured/the-conga-line-of-past-selves-a-string-liana-finck.html) - but that's really not the most interesting or powerful aspect of what `re-frame-10x` delivers.
### It Is About Trace Data
As it runs, `re-frame` logs "trace" as data, and this provides an x-ray (MRI?) of your app's inner
functioning. At its most basic level, `re-frame-trace` is a consumer, processor and presenter
functioning. At its most basic level, `re-frame-10x` is a consumer, processor and presenter
of trace data.
### It Is About The Data Flow
@ -33,7 +33,7 @@ what data is "happening".
### It Is Always About The Data
So, clearly, data is at the core of `re-frame-trace` for both of the reasons
So, clearly, data is at the core of `re-frame-10x` for both of the reasons
just outlined, but its importance is even more base and fundamental than that.
Each time you put a `println` into your program, you are printing out what?
@ -56,7 +56,7 @@ code and the data generated by running the code. The data provides a "paper trai
brings the code to life, revealing its dynamics and enriching
a programmer's understanding.
`re-frame-trace` has a similar goal, although the method is different.
`re-frame-10x` has a similar goal, although the method is different.
### It Is A Data Dashboard
@ -64,7 +64,7 @@ Observing raw data trace is both interesting and valuable, but it isn't enough.
First, we want to leverage this data for insights. And, second, there's often too much data - you
can drown in the detail.
So, `re-frame-trace` tries to be a "dashboard" which curates this
So, `re-frame-10x` tries to be a "dashboard" which curates this
"raw data" into "information" through various kinds of analysis
and "roll ups". It should deliver insight "at a glance", while still allowing
you to drill down into the detail.
@ -97,7 +97,7 @@ features, and build a cognative map of how the code is structured.
### Temporary Warning
> Some of the claims above are aspirational. `re-frame-trace` [remains a WIP](https://github.com/Day8/re-frame-trace/issues/118).
> Some of the claims above are aspirational. `re-frame-10x` [remains a WIP](https://github.com/Day8/re-frame-10x/issues/118).
## Of Sausage And Sizzle
@ -121,7 +121,7 @@ If you are using leiningen, modify `project.clj` in the following ways. When puz
- Update your re-frame dependency to at least `0.10.5` - `[re-frame "0.10.5"]`.
- Add re-frame-trace as a dev dependency by placing `[day8.re-frame/trace "VERSION"]` within `:profiles :dev :dependencies`. For example:
- Add re-frame-10x as a dev dependency by placing `[day8.re-frame/trace "VERSION"]` within `:profiles :dev :dependencies`. For example:
```cljs
:profiles
@ -149,7 +149,7 @@ If you are using leiningen, modify `project.clj` in the following ways. When puz
}}]}
```
[cljs-devtools](https://github.com/binaryage/cljs-devtools) is not required to use re-frame-trace, but it is highly recommended.
[cljs-devtools](https://github.com/binaryage/cljs-devtools) is not required to use re-frame-10x, but it is highly recommended.
## Usage
@ -179,7 +179,7 @@ If you are using leiningen, modify `project.clj` in the following ways. When puz
* Try a `lein clean`
* Make sure you have followed all the installation steps.
### If re-frame-trace throws an exception on startup
### If re-frame-10x throws an exception on startup
* Reset the settings to factory defaults in the settings panel
* If you can't load the settings panel, run `day8.re_frame.trace.factory_reset_BANG_()` in the JavaScript console.
@ -189,15 +189,15 @@ If you are using leiningen, modify `project.clj` in the following ways. When puz
re-frame is instrumented - all important activity generates trace data.
`re-frame-trace` consumes this trace data and renders useful visualisations of the `re-frame` process. Currently, re-frame's tracing capabilities are in alpha and are subject to change at any time. We're testing the utility of the the trace by building an app on top.
`re-frame-10x` consumes this trace data and renders useful visualisations of the `re-frame` process. Currently, re-frame's tracing capabilities are in alpha and are subject to change at any time. We're testing the utility of the the trace by building an app on top.
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](https://github.com/clojure/clojurescript/wiki/Compiler-Options#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 [make a PR to reagent to add proper hooks](https://github.com/Day8/re-frame-trace/issues/115), once we know exactly what we need. The preload namespace also injects a div containing the devtools panel into the DOM.
The [preloads](https://github.com/clojure/clojurescript/wiki/Compiler-Options#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 [make a PR to reagent to add proper hooks](https://github.com/Day8/re-frame-10x/issues/115), once we know exactly what we need. The preload namespace also injects a div containing the devtools panel into the DOM.
## Developing/Contributing
If you want to work on re-frame-trace, see [DEVELOPERS.md](DEVELOPERS.md).
If you want to work on re-frame-10x, see [DEVELOPERS.md](DEVELOPERS.md).
## Citations

8
docs/HyperlinkedInformation/Diffs.md
View File

@ -1,14 +1,14 @@
This document explains what you are seeing in sections
labelled "Only Before" and "Only After".
In various places, `re-frame-trace` allows you to inspect values like `app-db`.
In various places, `re-frame-10x` allows you to inspect values like `app-db`.
Knowing the current value is useful, but
you are sometimes more interested to know how a value has changed.
The value might be `X` before the start of this epoch, and
ended up as `X'`. So `re-frame-trace` will be showing you `X'` but you might woonder
ended up as `X'`. So `re-frame-10x` will be showing you `X'` but you might woonder
how `X` and `X'` are different. What got added or removed, and what was modified?
To show such differences, `re-frame-trace` chooses to do a calculation best explained by this pseudo code:
To show such differences, `re-frame-10x` chooses to do a calculation best explained by this pseudo code:
```clj
(let [[only-before only-after _] (clojure.data/diff X X')]
...)
@ -16,7 +16,7 @@ To show such differences, `re-frame-trace` chooses to do a calculation best expl
Remember `X` is the value immediately `before` (this epoch). And `X'` is the value `after` (the epoch has completed).
By [looking at the docs](https://clojuredocs.org/clojure.data/diff) for `clojure.data/diff`, you'll see
that it calculates how two values differ, and returns a triple of values. `re-frame-trace`
that it calculates how two values differ, and returns a triple of values. `re-frame-10x`
captures and displays the first two elements of this triple as "only before" and "only after"
respectively. The 3rd element is ignored because it's what hasn't changed, which isn't interesting.

8
docs/HyperlinkedInformation/InterEpoch.md
View File

@ -2,14 +2,14 @@
> "Music is the space between the notes." - Claude Debussy
`re-frame-trace` is built around the idea of epochs. An epoch captures all of the trace emitted by re-frame during the handling an event. But what about the trace emitted when re-frame *isn't* handling an event? These are the intra-epoch traces.
`re-frame-10x` is built around the idea of epochs. An epoch captures all of the trace emitted by re-frame during the handling an event. But what about the trace emitted when re-frame *isn't* handling an event? These are the intra-epoch traces.
Intra-epoch traces are emitted under (at least) three circumstances:
* Views sometimes have local state in the form of local ratoms which control, for example, the appearance of popups or mouseover annimations. When the state of these ratoms change, dependent views will likely rerender, and the trace to do with this rerendering will flow from reagent to `re-frame-trace`. But there'll be no "current" epoch to put it in. Because there was no event (just a pseudo event caused by the ratom reset)
* Views sometimes have local state in the form of local ratoms which control, for example, the appearance of popups or mouseover annimations. When the state of these ratoms change, dependent views will likely rerender, and the trace to do with this rerendering will flow from reagent to `re-frame-10x`. But there'll be no "current" epoch to put it in. Because there was no event (just a pseudo event caused by the ratom reset)
* A Figwheel recompile and subsequent code reload will cause all existing subscriptions to be destroyed, andwill trigger a complete re-render of your application. Again, a flood of trace to do with subscriptions and views will arrive but have no epoch home.
* `re-frame-trace` itself resetting the value in `app-db`. Once again, there will be a flurry of subscription and view trace, but no epoch, because there was no event.
* `re-frame-10x` itself resetting the value in `app-db`. Once again, there will be a flurry of subscription and view trace, but no epoch, because there was no event.
The first of these is essential to the functioning of your application, which probably makes the trace interesting and informative. The last two are incidental to the tooling and are probably best ignored. Probably.
`re-frame-trace` collects any intra-epoch subscription traces and shows them in the subs panel with the next epoch. They are broken out into a separate section marked: "Intra-Epoch Subscriptions".
`re-frame-10x` collects any intra-epoch subscription traces and shows them in the subs panel with the next epoch. They are broken out into a separate section marked: "Intra-Epoch Subscriptions".

2
docs/HyperlinkedInformation/README.md
View File

@ -1 +1 @@
The `re-frame-trace` UI contains hyperlinks to the various documents in this directory. Within the UI, these hyperlinks have text like "guide me to greatness" and "why?", which indicates the purpose of the docs herein.
The `re-frame-10x` UI contains hyperlinks to the various documents in this directory. Within the UI, these hyperlinks have text like "guide me to greatness" and "why?", which indicates the purpose of the docs herein.

6
docs/HyperlinkedInformation/ReplayButton.md
View File

@ -2,12 +2,12 @@ This document explains the operation of the "Replay" button, and how to use **Th
### Epoch Navigation
By using the backwards and forwards arrows, `re-frame-trace` allows you to navigate through Epochs.
By using the backwards and forwards arrows, `re-frame-10x` allows you to navigate through Epochs.
At any one moment, you are inspecting a single Epoch, for which we'll use the term "The Observed Epoch".
### On Click
When you click the "Replay" button, you are asking `re-frame-trace` to perform
When you click the "Replay" button, you are asking `re-frame-10x` to perform
an "Action Replay" of "The Observed Epoch", and this happens in two Steps:
- **Step 1** - the value in `app-db` is reset to the value it contained immediately prior to "The Observed Epoch"
- **Step 2** - the event which caused "The Observed Epoch" is re-dispatched
@ -27,7 +27,7 @@ So, Step 1 is "reestablish initial conditions" and Step 2 is "do it all again".
### Useful?
It facilitates "The HotPlay Workflow":
- A. You `Observe` an Epoch (in `re-frame-trace`) to see if an event was correctly processed
- A. You `Observe` an Epoch (in `re-frame-10x`) to see if an event was correctly processed
- B. You notice a problem, and you `Edit` (fix) the event handler (or subs handler, view, etc) via Cursive, Emacs, etc.
- C. Figwheel will re-compile and `Hotload` your correction
- D: You click the `Replay` button

4
docs/HyperlinkedInformation/UnchangedLayer2.md
View File

@ -35,7 +35,7 @@ Because `layer 2` subs run on every single modification of `app-db`, and because
very often nothing has changed, their trace can be a bit noisy. Yes, it happened,
but it just isn't that interesting.
So `re-frame-trace` gives you the option of filtering out trace for
So `re-frame-10x` gives you the option of filtering out trace for
the `layer 2` subscriptions where the value "this time" is the same as the
value "last time".
@ -45,7 +45,7 @@ be told all about it. :-)
### Why do I sometimes see "Layer ?" when viewing a subscription?
To determine whether a subscription is a layer 2 or layer 3, re-frame-trace
To determine whether a subscription is a layer 2 or layer 3, re-frame-10x
looks at the input signals to a subscription. If one of the input signals is
app-db then the subscription is a layer 2 sub, otherwise it is a layer 3. If
a subscription hasn't run yet, then we can't know if it is a layer 2 or 3.

8
docs/HyperlinkedInformation/UnderstandingTiming.md
View File

@ -1,4 +1,4 @@
Some notes on the "Timing" tab in `re-frame-trace`.
Some notes on the "Timing" tab in `re-frame-10x`.
## Be Sceptical Of The Numbers
@ -9,14 +9,14 @@ Two reasons:
takes 10ms, and you’ll never know why. Noisy.
So, don't ever draw conclusions from one set of timings.
Click the "replay" button ([#115](https://github.com/Day8/re-frame-trace/issues/155))
Click the "replay" button ([#115](https://github.com/Day8/re-frame-10x/issues/155))
a few times to ensure the numbers are stable.
2. Don't freak out about any apparent slowness. Not initially, anyway.
After all, you're running a dev build, right, not the
production build? And I'm guessing you're also
running a dev build of React? And `re-frame-trace` will itself also add
running a dev build of React? And `re-frame-10x` will itself also add
drag, what with all that creating and analysing of trace.
So, run the production version of your app first, before
@ -47,4 +47,4 @@ accurate timing figures.
Here is (React 16) advice on [debugging React performance with Chrome Devtools](https://building.calibreapp.com/debugging-react-performance-with-react-16-and-chrome-devtools-c90698a522ad)
The [re-frame.core/debug](https://github.com/Day8/re-frame/blob/master/src/re_frame/std_interceptors.cljc) interceptor is relatively slow, and runs interleaved with your application's events being processed. re-frame-trace gives you the same information in the app-db panel, but saves the calculations until after your application has finished running, so you don't get the performance cost included in your timing.
The [re-frame.core/debug](https://github.com/Day8/re-frame/blob/master/src/re_frame/std_interceptors.cljc) interceptor is relatively slow, and runs interleaved with your application's events being processed. re-frame-10x gives you the same information in the app-db panel, but saves the calculations until after your application has finished running, so you don't get the performance cost included in your timing.

2
docs/README.md
View File

@ -2,7 +2,7 @@
## App DB path expansions
re-frame-trace preserves path expansions by using the through the JSONML
re-frame-10x preserves path expansions by using the through the JSONML
that is rendered, rather than the actual data path. This has the advantage
of being feasible, but the disadvantage that if the HTML layout changes,
then that can trigger expansion changes. This means that if the map keys

2
docs/architecture-decisions/adr-001-epochs.md
View File

@ -8,7 +8,7 @@
Conceptually, re-frame is built around an event loop. The user makes an action, which causes an event to be dispatched, which changes app-db, which causes subscriptions to rerun, which causes the UI to update. We will refer to this cycle as an epoch. A user developing a re-frame application will want to be able to debug from this perspective.
Currently, re-frame-trace offers three panels: app-db, subs, and traces. Each of these offers a view into the application state and allows the programmer to build up a mental model of what is happening. They are not going to go away, but there is room for a more integrated and holistic panel.
Currently, re-frame-10x offers three panels: app-db, subs, and traces. Each of these offers a view into the application state and allows the programmer to build up a mental model of what is happening. They are not going to go away, but there is room for a more integrated and holistic panel.
### Requirements

6
project.clj
View File

@ -1,6 +1,6 @@
(defproject day8.re-frame/trace "0.1.23-SNAPSHOT"
:description "Tracing and developer tools for re-frame apps"
:url "https://github.com/Day8/re-frame-trace"
(defproject day8.re-frame/re-frame-10x "0.2.0-SNAPSHOT"
:description "Become 10x more productive when developing and debugging re-frame applications."
:url "https://github.com/Day8/re-frame-10x"
:license {:name "MIT"}
:dependencies [[org.clojure/clojure "1.9.0"]
[org.clojure/clojurescript "1.9.671"]

6
resources/day8/re_frame/trace/main.less
View File

@ -15,7 +15,7 @@
@text-color: #222;
@text-color-muted: #8f8f8f;
#--re-frame-trace-- {
#--re-frame-10x-- {
all: initial;
@ -236,7 +236,7 @@
}
/* re-frame-trace styles
/* re-frame-10x styles
========================================================================== */
@ -564,7 +564,7 @@
/* app-db data viewer
========================================================================== */
.re-frame-trace--object {
.re-frame-10x--object {
.toggle {
color: @text-color-muted;
cursor: pointer;

2
src/day8/re_frame/trace.cljs
View File

@ -213,7 +213,7 @@
(defn panel-div []
(let [id "--re-frame-trace--"
(let [id "--re-frame-10x--"
panel (.getElementById js/document id)]
(if panel
panel

2
src/day8/re_frame/trace/common_styles.cljs
View File

@ -150,7 +150,7 @@
(def blue-modern
[;; ========== Specific blue-modern styles (must be added to :class arg)
:#--re-frame-trace--
:#--re-frame-10x--
[:.bm-white-background {:background-color white-background-color
:border (str "1px solid " white-background-border-color)}]
[:.bm-standard-background {:background-color standard-background-color

4
src/day8/re_frame/trace/events.cljs
View File

@ -228,7 +228,7 @@
;; Global
(defn mount [popup-window popup-document]
(let [app (.getElementById popup-document "--re-frame-trace--")
(let [app (.getElementById popup-document "--re-frame-10x--")
doc js/document]
(styles/inject-trace-styles popup-document)
(goog.object/set popup-window "onunload" #(rf/dispatch [:global/external-closed]))
@ -248,7 +248,7 @@
d (.-document w)]
(.open d)
(.write d "<head></head><body style=\"margin: 0px;\"><div id=\"--re-frame-trace--\" class=\"external-window\"></div></body>")
(.write d "<head></head><body style=\"margin: 0px;\"><div id=\"--re-frame-10x--\" class=\"external-window\"></div></body>")
(goog.object/set w "onload" #(mount w d))
(.close d)))

10
src/day8/re_frame/trace/styles.cljs
View File

@ -28,7 +28,7 @@
(def css-reset
[:#--re-frame-trace--
[:#--re-frame-10x--
{:all "initial"}
[:* "*:before" "*:after"
{:all "unset"}]
@ -169,7 +169,7 @@
:z-index 1000})
(def re-frame-trace-styles
[:#--re-frame-trace--
[:#--re-frame-10x--
{:background-color common/background-gray
:font-family common/font-stack
:color text-color}
@ -405,7 +405,7 @@
:opacity "0.3"}]
[:.active {:opacity 1}]
[:.re-frame-trace--object
[:.re-frame-10x--object
[:.toggle {:color text-color-muted
:cursor "pointer"
:line-height 1}]
@ -430,7 +430,7 @@
(def panel-styles (apply garden/css [css-reset
[:#--re-frame-trace-- rc/re-com-css]
[:#--re-frame-10x-- rc/re-com-css]
common/blue-modern
re-frame-trace-styles
app-db/app-db-styles
@ -455,4 +455,4 @@
new-styles-el))))
(defn inject-trace-styles [document]
(inject-style document "--re-frame-trace-styles--" panel-styles))
(inject-style document "--re-frame-10x-styles--" panel-styles))

6
src/day8/re_frame/trace/utils/localstorage.cljs
View File

@ -14,7 +14,7 @@
(str safe-prefix key))
(defn get
"Gets a re-frame-trace value from local storage."
"Gets a re-frame-10x value from local storage."
([key]
(get key nil))
([key not-found]
@ -24,12 +24,12 @@
(reader/read-string value)))))
(defn save!
"Saves a re-frame-trace value to local storage."
"Saves a re-frame-10x value to local storage."
[key value]
(.set storage (safe-key key) (pr-str value)))
(defn delete-all-keys!
"Deletes all re-frame-trace config keys"
"Deletes all re-frame-10x config keys"
[]
(doseq [k (js/Object.keys js/localStorage)]
(when (str/starts-with? k safe-prefix)

2
src/day8/re_frame/trace/utils/utils.cljs
View File

@ -1,6 +1,6 @@
(ns day8.re-frame.trace.utils.utils)
(def diff-link "https://github.com/Day8/re-frame-trace/blob/master/docs/HyperlinkedInformation/Diffs.md")
(def diff-link "https://github.com/Day8/re-frame-10x/blob/master/docs/HyperlinkedInformation/Diffs.md")
(defn last-in-vec
"Get the last element in the vector"

2
src/day8/re_frame/trace/view/app_db.cljs
View File

@ -32,7 +32,7 @@
(def animation-duration 150)
(def app-db-styles
[:#--re-frame-trace--
[:#--re-frame-10x--
#_[:.app-db-path
{:background-color common/white-background-color
:border-bottom-left-radius border-radius

8
src/day8/re_frame/trace/view/components.cljs
View File

@ -126,7 +126,7 @@
(let [expanded? (rf/subscribe [:app-db/node-expanded? path])]
(fn [jsonml path]
[:span
{:class (str "re-frame-trace--object" (when @expanded? " expanded"))}
{:class (str "re-frame-10x--object" (when @expanded? " expanded"))}
[:span {:class "toggle"
:on-click #(rf/dispatch [:app-db/toggle-expansion path])}
[:button.expansion-button (if @expanded? "▼" "▶")]]
@ -172,7 +172,7 @@
:children
[[rc/h-box
:align :center
:class (str/join " " ["re-frame-trace--object"
:class (str/join " " ["re-frame-10x--object"
(when @expanded? "expanded")])
:children
[[:span {:class "toggle"
@ -193,7 +193,7 @@
(let [expanded? (r/atom true) #_(rf/subscribe [:app-db/node-expanded? path])]
(fn [data]
[:div
{:class (str/join " " ["re-frame-trace--object"
{:class (str/join " " ["re-frame-10x--object"
(when @expanded? "expanded")])}
#_[:span {:class "toggle"
:on-click #(rf/dispatch [:app-db/toggle-expansion path])}
@ -212,7 +212,7 @@
(let [expanded? (r/atom true) #_(rf/subscribe [:app-db/node-expanded? path])]
(fn [data]
[:div
{:class (str/join " " ["re-frame-trace--object"
{:class (str/join " " ["re-frame-10x--object"
(when @expanded? "expanded")
class])}
#_[:span {:class "toggle"

2
src/day8/re_frame/trace/view/event.cljs
View File

@ -11,7 +11,7 @@
(def border-radius "3px")
(def event-styles
[:#--re-frame-trace--
[:#--re-frame-10x--
[:.event-panel
{:padding "39px 19px 0px 0px"}]
[:.event-section]

2
src/day8/re_frame/trace/view/settings.cljs
View File

@ -15,7 +15,7 @@
(def settings-box-131 (render-css (units/px- common/gs-131 (units/px* 2 settings-box-vertical-padding))))
(def settings-styles
[:#--re-frame-trace--
[:#--re-frame-10x--
[:.settings
{:background-color common/white-background-color}]
])

6
src/day8/re_frame/trace/view/subs.cljs
View File

@ -96,7 +96,7 @@
:model ignore-unchanged-l2-subs?
:label [:span "Ignore " [:b {:style {:font-weight "700"}} @ignore-unchanged-l2-count] " unchanged" [:br]
[rc/link {:label (str "layer 2 " (utils/pluralize- @ignore-unchanged-l2-count "sub"))
:href "https://github.com/Day8/re-frame-trace/blob/master/docs/HyperlinkedInformation/UnchangedLayer2.md"}]]
:href "https://github.com/Day8/re-frame-10x/blob/master/docs/HyperlinkedInformation/UnchangedLayer2.md"}]]
:style {:margin-top "6px"}
:on-change #(rf/dispatch [:subs/ignore-unchanged-l2-subs? %])]]]]]))
@ -147,7 +147,7 @@
[rc/label :label (if (some? layer)
(str "Layer " layer)
[rc/link {:label "Layer ?"
:href "https://github.com/Day8/re-frame-trace/blob/master/docs/HyperlinkedInformation/UnchangedLayer2.md#why-do-i-sometimes-see-layer--when-viewing-a-subscription"}])]
:href "https://github.com/Day8/re-frame-10x/blob/master/docs/HyperlinkedInformation/UnchangedLayer2.md#why-do-i-sometimes-see-layer--when-viewing-a-subscription"}])]
[rc/gap-f :size common/gs-12s]
[rc/box
@ -301,7 +301,7 @@
[:h2 {:class "bm-heading-text"
:style {:margin "19px 0px"}}
[rc/link
{:href "https://github.com/Day8/re-frame-trace/blob/master/docs/HyperlinkedInformation/InterEpoch.md"
{:href "https://github.com/Day8/re-frame-10x/blob/master/docs/HyperlinkedInformation/InterEpoch.md"
:label "Inter-Epoch Subscriptions"}]]
(for [p inter-epoch-subs]

4
src/day8/re_frame/trace/view/timing.cljs
View File

@ -7,7 +7,7 @@
[day8.re-frame.trace.view.components :as components]))
(def timing-styles
[:#--re-frame-trace--
[:#--re-frame-10x--
[:.timing-details
{:margin-top common/gs-31s}]
[:.timing-details--line
@ -70,7 +70,7 @@
:style {:margin-left common/gs-19s}
:attr {:rel "noopener noreferrer"}
:target "_blank"
:href "https://github.com/Day8/re-frame-trace/blob/master/docs/HyperlinkedInformation/UnderstandingTiming.md"]]]
:href "https://github.com/Day8/re-frame-10x/blob/master/docs/HyperlinkedInformation/UnderstandingTiming.md"]]]
[rc/h-box
:gap common/gs-12s
:class "timing-part-panel"

2
src/mranderson047/re_frame/v0v10v2/re_frame/trace.cljc
View File

@ -29,7 +29,7 @@
[key f]
(if trace-enabled?
(swap! trace-cbs assoc key f)
(console :warn "Tracing is not enabled. Please set {\"re_frame.trace.trace_enabled_QMARK_\" true} in :closure-defines. See: https://github.com/Day8/re-frame-trace#installation.")))
(console :warn "Tracing is not enabled. Please set {\"re_frame.trace.trace_enabled_QMARK_\" true} in :closure-defines. See: https://github.com/Day8/re-frame-10x#installation.")))
(defn remove-trace-cb [key]
(swap! trace-cbs dissoc key)