observablehq / observablehq/plot
Allow hierarchical data for the tree (and related) marks?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- HTML
- Stars
- 5.4k
- Forks
- 244
- PR merge metrics
- No merged PRs in 30d
Description
We currently require you to provide tidy data to the tree mark, typically with a path column that provides a slash-delimited string representing the location of each row in the tree. It’d be nice if we also allowed D3’s nested {children} object representation, as is used by many D3 examples.
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 with the tree mark’s current path-column handling and compare it with D3’s nested {children} representation. Check how the related marks share this data path. Done means accepting nested hierarchical data while retaining the existing tidy-data behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- d3
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100