Add no-floating-promises options to tslint in order to ensure all promises are properly handled #3762
Conversation
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
Fatme
force-pushed
the
fatme/no-floating-promises
branch
from
f1c42aa to
974d665
Compare
…mises are properly handled
Fatme
force-pushed
the
fatme/no-floating-promises
branch
from
974d665 to
f25bccb
Compare
Contributor
Author
|
run ci |
2 similar comments
Contributor
Author
|
run ci |
Contributor
|
run ci |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Checklist
What is the current behavior?
grunt lintcommand does not print an error in case some await is missingWhat is the new behavior?
grunt lintcommand prints an error in case some await is missing