-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Vislib/axis #8254
Vislib/axis #8254
Conversation
This is pretty broken, so perhaps we should finish #8253 before moving to this? |
- splitting it into 3 subclasses (Axis, AxisLabels, AxisScale) - converting to ES6 classes + style fixes - adding more customization options
- allowing handler to have multiple category/value axes (array)
…f axis - updating css min-widths to 1px (removing them breaks the code) as we dont want to reserve the space for axes that dont exist.
300dfcc
to
727eecc
Compare
i am not sure what happened, either rebase went wrong or i forgot to commit some parts ... i am working on adding AxisConfig class now. what do you think its better, make it a commit here or should i make it a separate PR ? |
position: 'left', | ||
axisFormatter: null, // TODO: create default axis formatter | ||
scale: 'linear', | ||
expandLastBucket: true, //TODO: rename ... bucket has nothing to do with vis |
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.
👍
Alright, changes will be in the AxisConfig pr, and this looks good, so merging! |
replying work from #8174 to the new vislib-axis-refactor branch
i hope its not too messy, but i am guessing you are by now already quite familiar with this code so it might be easiest for both to start from here.
im gonna create a new PR now where i'll add AxisConfig class (to decouple Axis subclasses from Axis itself) which if i understood correcly is the biggest concert with the current implementation.