Issue #37 · Only facilitate LocalStorage at the top-level
- 2020 editor
- issue
On 28 May 2020 at 21:45:48 UTC, issue #37, “Only facilitate LocalStorage at the top-level,” was opened for OpenChronology’s earlier PureScript and React editor in the openchronology.github.io repository. **Archived issue text:** The only Signal that should be remembered (stored) in a session, is the one that basically backs-up the entire page data (except for navigation; that's encoded in the URL) - this would be the top-level parent signal, which would be an analogue to Timeline.Data (TimeSpaceDecided), but from a user-interface perspective (consideration for zoom level, etc.) The biggest consideration is, what constitutes the difference between user-interface-only data, and document-data? *Archived by the Wayback Machine on 15 September 2020; the repository has since been deleted from GitHub.* This moment records the request or report, rather than asserting that the proposed work was completed on its opening date. **Source:** [Project record](https://web.archive.org/web/20200915034605/https://github.com/openchronology/openchronology.github.io/issues/37).
Sources
Open Issue #37 · Only facilitate LocalStorage at the top-level in the timeline