scale.nice should be sticky, like scale.round?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- data-visualization
Research direction
Read the scale.nice and scale.round behavior discussed in the issue, then review the scale API and its tests to understand how domain changes are handled. The proposal is to remember the nice setting and apply it to new domains; decide how this should interact with the no-argument scale.nice() behavior and its backwards compatibility before implementation.
Written by the indexing model from the issue text.
Description
Currently, scale.nice only modifies the scale’s current domain; if you set a new domain, it won’t be niced. However, perhaps scale.nice should function more like scale.round, and remember the nice setting, such that any new domain that is set is automatically niced.
However, this would not be a backwards-compatible change, since it would affect the behavior of scale.nice() with no arguments: it would now return the current nice count, which would default to undefined indicating that the scale is not niced.
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 288
- Avg merge
- 6h 41m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from d3/d3-scale
-
The default tickFormat with a collapsed domain lacks sufficient precisionPossibly taken @Fil claimed this 877 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
scaleDiverging for domain [1,1,0] produces wrong resultsPossibly taken @Rajvira10 claimed this 26 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
assistant-ui/assistant-ui#10496 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
ai bug design good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
neomjs/neo-agent-institution#927 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gramps-project/gramps-web#1671 ·
Maintainers usually reply within 1 day
-
bug good first issue priority: P2 status: ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RhinoLink-Tech/data-fabric#502 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
cline/mcp-marketplace#3708 ·