#545 Let events carry tags of up to 128 characters
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#545
- pull request
- state:merged
Part of #538. Mirroring work items from self-hosted forges tags each item with its reference, for example `gitlab:git.example.com/group/subgroup/project!1234`. A 64-character tag can't always hold that. - **Event tags** may now be 1–128 characters. So may the tags that select events: separations and default views (`viewFilterKey`, `filterDocument`, the HTTP separation filter), chart series, and mapping filters. - **A timeline's own tags**, shown on cards and pages, stay within 64. The native store only checks those, so it is unchanged. - **New check:** `validateEntityTags` (with `ENTITY_TAG_LENGTH`) is the event-tag check. `validateTags` keeps its 64-character default. - **Schemas and docs:** the OpenAPI schemas for entity metadata, default views and separations allow 128. `docs/tags.md` says so. ## Tests A new test in `test/tags.test.mjs` covers both limits, an event keeping a 128-character tag, and a separation selecting by one. `npm test` passes apart from `contents.test.mjs`, which fails locally with git `ENOBUFS`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/pull/545
Related
- #538 Work-item sources: aggregate GitHub assignments, then Planner and kanban boards
- #546 Mirror Forgejo and Gitea, and commits, branches and forks (#538)
- #547 Mirror GitLab projects: issues, merge requests and commits (#538)
- Check separations' tags as events' tags, up to 128 characters
- Merge pull request #545 from openchronology/feature/entity-tag-length
Open #545 Let events carry tags of up to 128 characters in the timeline