Skip to content

Conversation

@erikreedstrom
Copy link

  • fixed timezone implementation for ISO8601 and RFC3339 formats
  • added ability to parse milliseconds in accordance with ISO8601/RFC3339
  • updated toISOString to output 3 digit milliseconds in accordance with RFC3339 format
  • added specs for new functionality

Other changes

  • removed build directory as newer frameworks typically contain asset pipelines and JS uglifiers
  • removed outdated changelist as it is no longer required
  • TODO updated

- fixed timezone implementation for ISO8601 and RFC3339 formats
- added ability to parse milliseconds in accordance with ISO8601/RFC3339
- updated toISOString to output 3 digit milliseconds in accordance with RFC3339 format
- added specs for new functionality

Other changes
- removed build directory as newer frameworks typically contain asset pipelines and JS uglifiers
- removed outdated changelist as it is no longer required
- TODO updated
@erikreedstrom
Copy link
Author

I was using rfc3339date.js as an overlay on DateJS, but have decided that I'd had enough of DateJS not parsing timezone/offset data. Full implementation of the standards is not complete, but covers a good 95% of use case scenarios.

@eric
Copy link
Owner

eric commented Jan 11, 2012

This looks great! Thanks!

eric added a commit that referenced this pull request Jan 11, 2012
Timezones and Timezone offsets now parse correctly
@eric eric merged commit 75fb8e8 into eric:next Jan 11, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants