This repository has been archived by the owner on Aug 8, 2024. It is now read-only.
Fixes the no-nested-ternary warning #691
Merged
Conversation
This file contains 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
adityathakurxd
requested review from
eswarclynn and
raviteja83
as code owners
|
@adityathakurxd is attempting to deploy a commit to the 100mslive Team on Vercel. A member of the Team first needs to authorize it. |
raviteja83
approved these changes
Jan 24, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If we setup the web sample locally and run the
yarncommand to get dependencies andyarn start, it shows the no-nested-ternary warnings.This PR fixes these warning by changing the expressions causing it.