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 ReplayButton.md

This commit is contained in:
Mike Thompson 2018-02-18 00:16:37 +11:00 committed by GitHub
parent ad084d45da
commit ddb0875171
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/HyperlinkedInformation/ReplayButton.md
View File

@ -9,11 +9,11 @@ an "Action Replay" of "The Observed Epoch", and this happens in two Steps:
2. the event which caused "The Observed Epoch" is re-dispatched 2. the event which caused "The Observed Epoch" is re-dispatched
Further Notes: Further Notes:
- In Step 1, the reset of `app-db` will trigger - In Step 1, the reset of `app-db` will trigger dominoes 4,5,6, causing
subscriptions and views to rerun, as the application returns to the "prior state" subscriptions and views to rerun, as the application returns to the "prior state"
but none of this trace is captured. It is all ignored. but none of this trace is captured. It is all ignored.
- All trace arising in Step 2 forms a normal, new Epoch. The (original) Observed Epoch is - All trace arising in Step 2 forms a normal, new Epoch. The (original) Observed Epoch is
still there untouched. still there, untouched.
- The new Epoch (Step 2) is added to the end of the existing Epoch list. It is the newest, most recent Epoch. - The new Epoch (Step 2) is added to the end of the existing Epoch list. It is the newest, most recent Epoch.
- The user is auto-navigated to view this new epoch. So the user - The user is auto-navigated to view this new epoch. So the user
immediately sees the results for this new Epoch - the timings etc. immediately sees the results for this new Epoch - the timings etc.