API: fix types for strict null checks #20909
Merged
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.
While experimenting with
ParseConfigHost
I noticed that not all parameters toreadDirectory
are always defined. This PR updates these parameter's type annotations.In addition I implemented a
CompilerHost
and noticed that I cannot simply return the result ofts.resolveModuleName(...).resolvedModule
fromCompilerHost.resolveModuleNames
because the returned array does not acceptundefined
values. The code that uses this array has checks for undefined values, so I figured the return type annotation is not correct.