Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
refactor(parser): Remove
_bootstrap
method #384refactor(parser): Remove
_bootstrap
method #384Changes from 1 commit
ffa6722
3db52a2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is it intentional that the value can’t be
undefined
, but that the field can be missing?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 values can still be explicitly undefined — I am honestly not sure why the
| undefined
was here in the first place (this was copied from the previous @types package). My suspicion would be an older TS version?The only difference is that now
Required<>
works with the options.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 know that DefinitelyTyped was adding explicit
| undefined
to types, when they had?
. They‘re planning to pull them apart: DefinitelyTyped/DefinitelyTyped@b24e5f6.My recommendation is to add
| undefined
if the value can be set toundefined
. And to use?
when the field can be missing. And to use both, for both.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.
Ahh, thanks for digging this up. Looks like the option is now called
exactOptionalPropertyTypes
and is explicitly opt-in (no longer enabled withstrict
): microsoft/TypeScript#44626My intuition is that users enabling this flag wouldn't want to be able to pass
undefined
here.