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
test(config): remove strictNullChecks errors from compiler/config #3335
test(config): remove strictNullChecks errors from compiler/config #3335
Changes from 11 commits
57f87ff
4f64b8a
f748d28
d42d9b7
8b8b314
ab9f680
fd2dbbc
2a9ec5b
85acf7b
9c536ed
fba2ade
c724aff
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.
I'm not sure why we changed this key name here. Should this be
'esm'
still?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 wasn't sure about that - this argument is supposed to be of type
keyof d.ConfigFlags
andesm
is not a property onConfigFlags
so, assuming thatConfigFlags
objects actually conform to that interface there shouldn't ever be a value under the"esm"
key to pull out - I changed it for that reason, but it could be the case that we should keep it any, if we wanted to I think we'd need to add anesm: boolean
prop toConfigFlags
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.
Hmmm looks like this line (with the
flagName
set to'esm'
was added in a big refactor commit. I can't find a case where we use 'esm' as a property accessor on a config object directly (although that doesn't cover something likeconfig[someVarWhoseValueIsStringEsm]
. I smoke tested this against the output of create-stencil and couldn't see anything immediately obvious.My vote is we keep this change as is, and if we need to back it out we'll do just that