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
fix: save methods of children Date instance (#437) #480
base: main
Are you sure you want to change the base?
Conversation
Oooh, I somehow missed that this was added. Sorry about the late look, but while this is interesting, my head is a bit fried 🤯 This is quite a big change, so I (or someone else with a bigger head) needs to take a new look with a fresh head! Thanks for providing a fix to something that bugged you a year ago. That's persistence we can appreciate 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit scary breaking change, so I think I would like some more 👀 on this before going ahead.
@@ -3221,7 +3221,7 @@ describe("FakeTimers", function () { | |||
assert.equals(fakeDateStr, new this.clock.Date().toString()); | |||
}); | |||
|
|||
it("mirrors native Date.prototype", function () { | |||
it.skip("mirrors native Date.prototype", function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we could change this to be a test that it passes an instanceof check. it("is a Date instance", ...
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just kill the test. It would just be this in the end:
node -p 'class FooDate extends Date {}; D=Date; global.Date = function(){}; (new FooDate()) instanceof D'
true
@@ -3103,7 +3103,7 @@ describe("FakeTimers", function () { | |||
assert(typeof date === "string"); | |||
}); | |||
|
|||
it("creates real Date objects when Date constructor is gone", function () { | |||
it.skip("creates real Date objects when Date constructor is gone", function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test does not seem very useful. I would check the Git history for references.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dug back, found it was just copied over from Sinon ten years ago, so can't be bothered to look deeper:
Oustinger@dbd7d17#diff-7c9e5e3f3dd46601b73d2d05be43d6d7a33f2f7ccd564494f4eb7b3f4ae915e0R636
The only meaningful bit here about the test is that we check that everything still works as before. So the result of the toString should be the same before and after the removal of the global Date.
I started reviewing it and came to the "bit scary" conclusion as well. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stepan, I took a fresh new look at this and with rested eyes (and a lot of time - sorry), I don't think this looks all that controversial. I get the changes and I think it makes sense. All meaninful tests are running, so I would like to get this in.
If you read this anytime soon, do you think you could be bothered to just implement the very small changes?
const ClockDateProxy = new Proxy(ClockDate, { | ||
apply(Target, thisArg, argumentsList) { | ||
// the Date constructor called as a function, ref Ecma-262 Edition 5.1, section 15.9.2. | ||
// This remains so in the 10th edition of 2019 as well. | ||
if (!(this instanceof ClockDate)) { | ||
return new NativeDate(ClockDate.clock.now).toString(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
had to do a little brush up on Proxy objects and its apply to grok the logic, which made me pay so much attention to the details that I failed to see the toString()
bit. That was until I actually read section 15.9.2:
When Date is called as a function rather than as a constructor, it returns a String representing the current time (UTC).
Ooh. Did not remember this. Had to check:
❯ node -p 'Date(2023,01,10)'
Sat Feb 10 2024 11:54:24 GMT+0100 (GMT+01:00)
❯ node -p 'typeof Date(2023,01,10)'
string
I'd rather extract that into a silly, but aptly named, little method called currentDateTimeAsString()
and stuff all the details there, though! Makes small minds as my own able to grok the bigger picture faster. Makes for quicker 🆗 on PRs 😅 I know the bit of code was already there, though, so no worries!
// Defensive and verbose to avoid potential harm in passing | ||
// explicit undefined when user does not pass argument | ||
if (arguments.length === 0) { | ||
super(ClockDate.clock.now); | ||
} else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe cover this with a test? 🤔
@@ -3103,7 +3103,7 @@ describe("FakeTimers", function () { | |||
assert(typeof date === "string"); | |||
}); | |||
|
|||
it("creates real Date objects when Date constructor is gone", function () { | |||
it.skip("creates real Date objects when Date constructor is gone", function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dug back, found it was just copied over from Sinon ten years ago, so can't be bothered to look deeper:
Oustinger@dbd7d17#diff-7c9e5e3f3dd46601b73d2d05be43d6d7a33f2f7ccd564494f4eb7b3f4ae915e0R636
The only meaningful bit here about the test is that we check that everything still works as before. So the result of the toString should be the same before and after the removal of the global Date.
@@ -3221,7 +3221,7 @@ describe("FakeTimers", function () { | |||
assert.equals(fakeDateStr, new this.clock.Date().toString()); | |||
}); | |||
|
|||
it("mirrors native Date.prototype", function () { | |||
it.skip("mirrors native Date.prototype", function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just kill the test. It would just be this in the end:
node -p 'class FooDate extends Date {}; D=Date; global.Date = function(){}; (new FooDate()) instanceof D'
true
Fix issue #437 by creating ClockDate as JS class and extending it from NativeDate
Why I did this way:
ClockDate
by JS function)ClockDate
can't be correct instance to extend from it. That's why I replaced function on class. And it resolved my problem.Date()
withoutnew
keyword I solved by usingProxy
instance.mirrorDateProperties
function. It's not needed any more.But I had some troubles with tests:
ClockDate.prototype
never equals toDate.prototype
, becauseClockDate
is extended fromDate