#9276- Literals should not be used for promise rejection #9276iterals should not be used for promise rejection #9277
Open
oguzhanduran wants to merge 1 commit intomasterfrom
Conversation
auto-assign
bot
requested review from
AlexeyGirin,
NataliaLoginova and
svvald
oguzhanduran
force-pushed
the
9276-literals-should-not-be-used-for-promise-rejection
branch
from
3aa350e to
23898d0
Compare
9 tasks
Contributor
|
@oguzhanduran I've opened a new pull request, #9285, to work on those changes. Once the pull request is ready, I'll request review from you. |
oguzhanduran
force-pushed
the
9276-literals-should-not-be-used-for-promise-rejection
branch
from
23898d0 to
84b864a
Compare
oguzhanduran
force-pushed
the
9276-literals-should-not-be-used-for-promise-rejection
branch
from
84b864a to
e3168f4
Compare
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 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.
How the feature works? / How did you fix the issue?
(Screenshots, videos, or GIFs, if applicable)
Check list
#1234 – issue name