Time ranges

[samussiah]

Issues

Closes #140

[danedexF5]

@pburnsdata Ok so should I use lucky-charms to test this instead of time-ranges?

[pburnsdata]

@danedexF5 Yeah if it works there, then should be fine.

[danedexF5]

@samussiah tested in all 3. If "default" is what we want for the drop down option as mentioned below, then I think this is good. Also, I sued the lucky-charms branch to test this per Preston's notes.

• When I add the block {time_scale: 'date', date_range: ['2015-01-01', '2017-01-01']} the new option I get on the drop down is "default"
• When I add the block {time_scale: 'date', date_ranges: [{label: 'this is a date range', domain: ['2015-01-01', '2017-01-01']}]} the option I get on the drop down is "this is a date range"
• When I add the block {time_scale: 'day', day_range: [0,400]} the option I get on the drop down is "default"
• When I add the block {time_scale: 'day', day_ranges: [{label: 'this is a day range', domain: [0,400]}]} the option I get on the drop down is "this is a day range"
• When I alter start or end, the Time Range toggles to User Input

[samussiah]

@danedexF5 , those are the expected behaviors but I've gone back in and labeled date_range/day_range Initial Date/Day Range to be more transparent. When the Start/End controls change the Time range dropdown should change to User Input.