-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Update for TS 5.6 #3221
Update for TS 5.6 #3221
Conversation
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.
Ah, these files are now generated
<p>Initializes a TypeScript project and creates a tsconfig.json file.</p> | ||
</td></tr> | ||
|
||
<tr class='odd' name='listFilesOnly'> | ||
<tr class='even' name='listFilesOnly'> |
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 in this PR but one day https://developer.mozilla.org/en-US/docs/Web/CSS/:nth-child
@@ -834,12 +840,13 @@ | |||
"esnext.decorators", | |||
"esnext.object", | |||
"esnext.regexp", | |||
"esnext.iterator", | |||
"decorators", | |||
"decorators.legacy" | |||
] | |||
}, | |||
{ |
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 for my understanding, could you tell me what these pattern changes mean?
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.
These options are case insensitive, so this is just the absolutely ridiculous regex to verify the union of a bunch of strings
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.
In a better world, the regex syntax would accept syntax like (?i)
, but JS doesn't have that syntax, it puts it outside the regex expression and a load of consuming tools do not parse out strings like "/blah/i"
I had most of this change locally already while testing a 5.7 PR.