Skip to content

1.1.0

Compare
Choose a tag to compare
@nadnoslen nadnoslen released this 23 Oct 17:36
· 55 commits to main since this release

Upgrade From 1.0.x:

Upgrade will be relatively smooth. I'd suggest making sure your bower.json is purged of any moment, moment-timezone, and datejs-parse-plus libraries. These are no longer imported through bower. If you're somehow using the Date#parsePlus(...) function I created...understand it is gone. See the sugar.js parsing documentation instead OR continue to import the datejs-parse-plus library via bower...the choice is yours.

I also suggest that if you were using moment as a global variable...now change all those usages to actually import moment from 'moment'. This can be done with a pretty simply find on your project.

Sorry for the changes...but it's better in the long run.

Library Overhaul:

  • now using ember-moment add-on rather than pulling momentjs in through bower.
  • now using sugar.js to parse dates in the past and the future. A few parsing options have been lost with this shift from the old date.js library; e.g. '+30 minutes' is now 'in 30 minutes'. A small trade-off for modernizing the parse library and abandoning the forked date.js.

New Features:

  • now supporting actions for beforeParse, afterParseFail, and afterParseSuccess. Passing actions to these arguments will be triggered at the appropriate time of the parse routine. Your supplied action should expect the component as it's only argument. You can access all properties of the input-date or input-iso8601 at that time. For example, you might want to remove or add style classes on success or failure.
  • now supporting the endOfDay? and startOfDay? arguments. These do just as they imply, upon parsing the time component will be set accordingly.

Milestone Issues

Check out the issues here.