circagraph
Sign inSign up

How OpenChronology was built

Every merged pull request of openchronology/timeline-app, its first week of commits and its releases; and before them the 2020 PureScript editor, from snapshots of its deleted repositories in the Wayback Machine. Written to this server through the HTTP API.

327 moments · 2020-03-09 CE 00:15:08 UTC – 2026-11-02 CE 20:11:21 UTC · by @athan · @athan

Issue #31 · Consistent component modules

  • 2020 editor
  • issue

On 13 May 2020 at 15:41:16 UTC, issue #31, “Consistent component modules,” was opened for OpenChronology’s earlier PureScript and React editor in the openchronology.github.io repository. The proposal asks for consistency in component-module structure, including typed styles, public exports, declaration ordering and explicit signal or queue prerequisites. Its purpose is to make similar components easier to understand and maintain, including their dependencies. **Archived issue text:** The code is slightly varying between the components - there should be some standardization between them: - mostly typed style declaration, at the top-level - only exposing the components needed - "prerequisites" in terms of signals and queues (for machine readable graph generation) - ordering of declarations *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/20200915034600/https://github.com/openchronology/openchronology.github.io/issues/31).

Sources

Open Issue #31 · Consistent component modules in the timeline