-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Feature range slider #336
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
Feature range slider #336
Conversation
role: 'style', | ||
description: 'Sets the background color of the range slider.' | ||
}, | ||
height: { |
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.
let's go with thickness
here.
module.exports = { | ||
visible: { | ||
valType: 'boolean', | ||
dflt: false, |
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.
A blank range slider ( layout.xaxis.rangeslider = {}
) should be considered visible.
containerOut = layoutOut.xaxis.rangeslider = {}; | ||
|
||
if(!containerIn.visible) return; | ||
var containerIn = typeof layoutIn[axName].rangeslider === 'object' ? |
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.
use isPlainObject
instead.
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.
ah never mind. if layoutIn[axName].rangeslider
is null
it won't get to that part.
@@ -80,6 +81,7 @@ module.exports = { | ||
'January 1st 1970 to November 4th, 2013, set the range from 0 to 1380844800000.0' | ||
].join(' ') | ||
}, | ||
rangeslider: rangeSliderAttrs, |
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.
🎉
💃 |
Wooo! |
This is a decent sized PR, and likely will take a while to completely review and have things changed before being ready to merge, so we may as well get started.