This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 408
FakeDate does not accept a timestamp value #1069
Comments
@EoinF , thank you for posting the issue, I will try to fix this one. |
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 5, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 5, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 5, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 5, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 5, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 5, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 5, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 6, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 6, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 6, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 6, 2018
JiaLiPassion
added a commit
to JiaLiPassion/zone.js
that referenced
this issue
Apr 6, 2018
mhevery
pushed a commit
that referenced
this issue
Apr 6, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected Behaviour: Passing a timestamp value into the Date object, as shown below, will produce a Date with that timestamp
Actual Behaviour: The timestamp is ignored and the current Date is used
In later versions (0.8.21 and onwards) this is happening, while using fakeAsync(worked with 0.8.20 and earlier)
The following code sample demonstrates this:
The output is:
The first line of output is using the FakeDate object which is ignoring the value passed in and just producing the current Date.
The second line is working as expected.
This only occurs inside an async block, after an 'await' has been used
The text was updated successfully, but these errors were encountered: