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

Handle uncommon output from Date#toTimeString. #303

Merged
merged 1 commit into from
Mar 1, 2016

Conversation

timrwood
Copy link
Member

Addresses #294

@dominicbarnes
Copy link

Just curious, what is the expected output going to be now? Is it just going to return null or false? Or is something going to be chosen as the default timezone? (like "UTC")

In either case, can the tests being added here cover what the return value should be?

@timrwood
Copy link
Member Author

timrwood commented Mar 1, 2016

The expected output is that OffsetAt#abbr is undefined when we were unable to find an abbreviation from the builtin Date object.

A test would be good, but this class isn't exposed publicly at all, so it currently isn't possible to test the exact output. Moving to ES6 modules as noted in #298 would make explicit tests for this possible.

timrwood added a commit that referenced this pull request Mar 1, 2016
Handle uncommon output from Date#toTimeString.
@timrwood timrwood merged commit 839a495 into moment:develop Mar 1, 2016
@timrwood timrwood deleted the fix-to-time-string-errors branch March 1, 2016 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants