Chart.js time scale missing per-dataset timezone

Chart.js time scale 'time' type missing per-dataset timezone

0 reputation · 08 Sept 2023, 06:56 UTC

74.4K views0

Chart.js v4 time scale 'time' type currently enforces a single global timezone across all datasets, preventing per-dataset timezone specification.

Developers must preprocess timestamps to align with the global zone, which introduces bugs and extra processing when handling multi‑region data, and any API change to expose per-dataset timezones could break large existing codebases.

Is there a viable approach to add per-dataset timezone support without breaking existing configurations? Should the API be extended in a future major release to expose this capability? How can developers currently work around the limitation while preserving data integrity?

957 following

Keep exploring this topic

Kibana Timezone Configuration for Multi-Regional User Access

Exploration of Kibana's global timezone settings and the limitations of managing regional time zone offsets for multi-regional teams.

Chart.js legend callbacks: unresolved dataset visibility toggle timing

Chart.js legend callbacks exhibit inconsistent dataset visibility toggle timing across major versions, causing custom callbacks to misinterpret the hidden flag. This question explores the unresolved behavior and seeks guidance on handling the toggle order in configuration.

Jekyll timezone configuration: evaluating per‑post override support

Discussing whether Jekyll should support per‑post timezone overrides in front matter to complement its site‑wide timezone setting.

Google Colab Runtime Timezone – No Persistent TZ Setting

Google Colab’s runtime uses UTC and lacks a persistent timezone setting. Users can temporarily set TZ, but UI timestamps convert to browser local time, causing mismatches. What features could resolve this?

Chart.js time scale 'time' type missing per-dataset timezone

0 answers

Your perspective belongs here.

0 question comments