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

Update InterEpoch.md

This commit is contained in:
Mike Thompson 2018-02-10 15:00:57 +11:00 committed by GitHub
parent 32470d0324
commit b7e8fa5528
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/HyperlinkedInformation/InterEpoch.md
View File

@ -1,10 +1,10 @@
# Inter Epoch Traces # Intra Epoch Traces
> "Music is the space between the notes." - Claude Debussy > "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 traces emitted by re-frame during the handling an event. But what about the traces that are emitted when re-frame *isn't* handling an event? These are the inter-epoch traces. `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.
Inter-epoch traces are emitted under (at least) three circumstances: Intra-epoch traces are emitted under (at least) three circumstances:
* When views have local ratoms, used, for example, to handle the appearance of popups or mouseover annimations. When the state of these ratoms change, 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. * When views have local ratoms, used, for example, to handle the appearance of popups or mouseover annimations. When the state of these ratoms change, 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.
* A Figwheel recompile and subsequent code reload will cause all existing subscriptions to be destroyed, andwill trigger a complete re-render of your application * A Figwheel recompile and subsequent code reload will cause all existing subscriptions to be destroyed, andwill trigger a complete re-render of your application
@ -12,4 +12,4 @@ Inter-epoch traces are emitted under (at least) three circumstances:
The first of these is essential to the functioning of your application, whidh makes their trace interesting and informative. The last two are incidental to the tooling and are probably best ignored. Probably. The first of these is essential to the functioning of your application, whidh makes their trace interesting and informative. The last two are incidental to the tooling and are probably best ignored. Probably.
`re-frame-trace` collects any inter-epoch subscription traces and shows them in the subs panel with the next epoch. They are broken out into a separate section marked: "Inter-Epoch Subscriptions". `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".