Skip to content

Data-date chip under the Source list (UNHRDB and UHRI+) - #11

Merged
lszoszk merged 1 commit into
mainfrom
data-asof-chips
Oct 13, 2026
Merged

lszoszk merged 1 commit into
mainfrom
data-asof-chips

Conversation

@lszoszk

@lszoszk lszoszk commented Oct 13, 2026

Copy link
Copy Markdown
Owner
  • New chip (#data-asof) under the Source list. It repaints when the source changes:
    • UNHRDB sources: "Data updated 26 Sep 2026". This is the live API's build date (/api/stats manifest). When the API is offline it falls back to the static manifest.
    • Recommendations: "Recommendations to 9 Jul 2026 · checked 13 Oct 2026". This is the newest UHRI recommendation and the last check of OHCHR for new ones. It reads /uhri-api/refresh_status.json and /api/data/health; both already send CORS headers for lszoszk.github.io. The tooltip explains the publication lag.
  • Cache busting: app.js / app.css are now ?v=20261013-asof.

Tested

  • Full chromium suite: 135 passed, 1 skipped, 1 flaky. The flaky one, docs-reader R4b, passed on retry and doesn't touch the chip.
  • Local preview, UNHRDB path: the chip shows the static manifest date.
  • Recommendations path: checked with the two endpoints mocked, because CORS blocks localhost.

🤖 Generated with Claude Code

…ta last changed

UNHRDB sources: "Data updated 26 Sep 2026", the live API's build date (the static manifest's when the API is
offline). Recommendations: "Recommendations to 9 Jul 2026 · checked 13 Oct 2026", the newest UHRI
recommendation and the last check of OHCHR for new ones, from the mirror's refresh_status.json and
/api/data/health. The tooltip explains the lag. Repaints on a source switch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lszoszk
lszoszk merged commit fdb4b86 into main Oct 13, 2026
2 checks passed
@lszoszk
lszoszk deleted the data-asof-chips branch October 13, 2026 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant