| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Just a quick look
Sorry, something went wrong.
There was a problem hiding this comment.
Some performance / personal preference comments.
Overall this PR seems fine, although I'm unsure how it affects performance in different scenarios.
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good. I think couple of new tests for improved functionality would be good.
Sorry, something went wrong.
* 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
| Back | FazBrowse Home | New Git URL |
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 again
This 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 initial buildTicks step, the results include more ticks.
Interactive examples:
Closes #4600 #4612