Repository navigation
EXCEPTION: Invalid argument '2017-01-11T09:25:14.014-0500' for pipe 'DatePipe' #13874
Description
I'm submitting a ... (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
Using date pipe in IE doesn't work it throws an error message in console:
EXCEPTION: Invalid argument '2017-01-11T09:25:14.014-0500' for pipe 'DatePipe'
I have seen there are several open issue regarding date Pipe. But, they are representing the incorrect format. Whereas, the date pipe is not working at all in my case.
Expected behavior
The date pipe show work for:
'2017-01-11T09:25:14.014-0500' | date: 'MM/dd/yyyy hh:mm:ss a'
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
- Angular version: 2.0.X
- Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
-
Language: [all | TypeScript X.X | ES6/7 | ES5]
-
Node (for AoT issues):
node --version=
Activity
DzmitryShylovich commentedon Jan 11, 2017
@anvesh48
Open console in IE and try to create a date from your string
it's not a valid date in IE.
intellix commentedon Jan 11, 2017
Also not a valid date in Safari. Funnily enough neither is this:
new Date("2017-01-06 23:07:57")Safari is a joke
anrepppp commentedon Jan 11, 2017
@DzmitryShylovich You are right. But angular1 worked with the same date format.
Toxicable commentedon Jan 12, 2017
@anvesh48 This isn't Angular1
anrepppp commentedon Jan 12, 2017
@Toxicable Ok, I agree this is not Angular1..!
fix(common): DatePipe parses input string if it's not a valid date in…
fix(common): DatePipe parses input string if it's not a valid date in…
angular-automatic-lock-bot commentedon Sep 10, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.