Enable strict null checking for node/flow test - #65541
Merged
Benjamin Pasero (bpasero) merged 4 commits intoDec 21, 2018
Merged
Conversation
|
|
This reverts commit 4f0c4be.
Contributor
|
Looks like there are conflicts. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Related to #65233
Makes it so that
./vs/base/test/node/flow.test.tscan utilize strict null checks without errors.src/vs/base/node/flow.tswas the file changed instead because the errors in the test file were related to the types in parallel's function arguments.