Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

log.tickFormat(count, specifier) doesn’t set the precision. #42

Closed
mbostock opened this issue Dec 24, 2015 · 2 comments · Fixed by #254
Closed

log.tickFormat(count, specifier) doesn’t set the precision. #42

mbostock opened this issue Dec 24, 2015 · 2 comments · Fixed by #254

Comments

@mbostock
Copy link
Member

The documentation says it does:

If the specifier does not have a defined precision, the precision will be set automatically by the scale, returning the appropriate format.

But, it doesn’t. It probably should.
@mbostock mbostock self-assigned this Jun 11, 2016
@mbostock
Copy link
Member Author

If you’re using base 10 then typically you want something like ".1r" anyway…

@mbostock mbostock removed their assignment Jun 24, 2016
@mbostock mbostock self-assigned this Feb 9, 2017
@mbostock
Copy link
Member Author

mbostock commented Feb 9, 2017 •
edited
Loading

We should at least special-case this for base 10, because it’s annoying that axis.ticks(null, "s") works for linear scales but not log scales.

@mbostock mbostock removed their assignment Sep 2, 2019
@mbostock mbostock mentioned this issue Feb 24, 2021
Closed
This was referenced Sep 18, 2021
Open
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

implicit trim for log ticks d3/d3-scale
1 participant
@mbostock