observablehq / observablehq/plot
A top-level timeZone option
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 5.4k
- Forks
- 244
- PR merge metrics
- No merged PRs in 30d
Description
Related #384, what if instead of “time” (local time) and “utc” (UTC time) scales, we supported a top-level timeZone option that affected the interpretation of any “time” scales. For example, you could explicitly set the time zone to “America/Los_Angeles” so that all viewers see the same time zone. (Caveat: until JavaScript has built-in support for time zone math, it’s probably not practical to implement this.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading related issue #384 and inspect how the existing “time” and “utc” scales interpret dates. Determine whether a top-level timeZone option can consistently affect all “time” scales given the JavaScript time-zone limitation. Done means viewers see the same explicitly selected time zone across those scales.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100