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.

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

Merged
merged 8 commits into from
Sep 14, 2016
Merged

Vislib/axis #8254

merged 8 commits into from
Sep 14, 2016

Conversation

ppisljar
Copy link
Member

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.

@ppisljar ppisljar added the Feature:Vislib Vislib chart implementation label Sep 13, 2016
@spalger
Copy link
Contributor

spalger commented Sep 14, 2016

This is pretty broken, so perhaps we should finish #8253 before moving to this?

@spalger spalger removed the review label Sep 14, 2016
- 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.
@ppisljar
Copy link
Member Author

i am not sure what happened, either rebase went wrong or i forgot to commit some parts ...
anyway this should now be at the same stage vislib/axis was before ... so everything should work like it did before applying any changes to the vislib.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@spalger
Copy link
Contributor

spalger commented Sep 14, 2016

Alright, changes will be in the AxisConfig pr, and this looks good, so merging!

@spalger spalger merged commit cb9b937 into elastic:vislib-axis-refactor Sep 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Vislib Vislib chart implementation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants