-
Notifications
You must be signed in to change notification settings - Fork 1
fix: align ISODate with shell COMPASS-4655 #199
Conversation
@@ -2,8 +2,8 @@ | |||
"compilerOptions": { | |||
/* Basic Options */ | |||
// "incremental": true, /* Enable incremental compilation */ | |||
"target": "es5", /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019' or 'ESNEXT'. */ | |||
"module": "es2015", /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */ | |||
"target": "ES2018", /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019' or 'ESNEXT'. */ |
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.
should be safe at this point? helps with regex groups
package-lock.json
Outdated
"lockfileVersion": 2, | ||
"requires": true, | ||
"packages": { | ||
"": { | ||
"name": "ejson-shell-parser", | ||
"version": "2.0.0", | ||
"version": "2.0.1", |
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.
We still do releases through npm version patch && git push origin main --tags
?
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.
Not sure. I don't think I've released this in years, how does it relate to this line?
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 just means we usually do the version bumps outside of PRs 🙂 Definitely not a big deal (hence the approval), you can do it whichever way you want
Yeah, this package uses yarn, I think the package lock/yarn lock changes here are being rejected by it 🥴 |
Currently we treat
IsoDate
asDate
.IsoDate
works differently and always construct dates ignoring the current time zone if one is not specified.The code in the PR is copy-pasted from mongosh to make sure we address this type in the same way.