-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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.
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
Make autoskip aware of major ticks #6509
Conversation
2b6f0ef
to
bbf5ce5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a quick look
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some performance / personal preference comments.
Overall this PR seems fine, although I'm unsure how it affects performance in different scenarios.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I think couple of new tests for improved functionality would be good.
* Make autoskip aware of major ticks * Address review comments * Fix codeclimate warning * Add test for major and minor tick autoskipping * Revert change for determining _majorUnit and fix sample
I'm reopening #6274, which was partially reviewed earlier. I had closed it because I discovered a performance regression. Current
master
generates only the required ticks / labels. This PR generates a tick at every unit and then runs the auto-skipper to keep only the ones that we need. This has some benefits (see the last bullet below), but caused label generation to be more expensive. However, that is now being addressed by #6508, so I feel comfortable moving forward with this PR againThis PR does the following:
There's a handful of tests that have been changed because they test
buildTicks
. We're now building more ticks and then skipping the ones we don't need. Since the tests don't take into account the auto-skipping and are looking only at the initialbuildTicks
step, the results include more ticks.Interactive examples:
Closes #4600 #4612