circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#66 Fix: writers couldn't open API-created server timelines

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#66
  • pull request
  • state:merged

`GET /api/timelines/ ` reports settings a timeline never had as `null`. Timelines created through the API store no timeline tags (`tags` is NULL). That covers bench seeds, API ingestion, and the new syslog receiver. When a **writer** opened one, the editor built its `RemoteWorkspace` with `tags: null`, and the index constructor called `validateTags(null)`. That failed with the misleading toast "Use at most 40 tags." and left the page on "Loading timeline…". - Anonymous viewers weren't affected, because they don't build a writable workspace. - Timelines saved from the editor weren't affected either, because they store an empty tag list. **Fix:** `TimelineIndex` treats `null` `tags`, `assets` and `plugins` as absent, the way it already treated `presentation`. **Test:** `test/remote-cache.test.mjs` builds a workspace from metadata with null settings. It fails before the fix ("Use at most 40 tags.") and passes after. All unit tests pass (200). Found while building the UI benchmarks for #51. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Ti36soiZpKdSxKfvQLEcfY https://github.com/openchronology/timeline-app/pull/66

Related

Open #66 Fix: writers couldn't open API-created server timelines in the timeline

#66 Fix: writers couldn't open API-created server timelines