ref(tracing): Remove nullish coalescing operator and add eslint rule#6783
Merged
ref(tracing): Remove nullish coalescing operator and add eslint rule#6783
Conversation
Contributor
size-limit report 📦
|
Member
|
Should we maybe also add an eslint rule for this? 🤔 Similar to #6777 |
Member
Author
Sounds good to me. Will do in a bit |
AbhiPrasad
approved these changes
Jan 16, 2023
71d1e54 to
54052c6
Compare
54052c6 to
afa978b
Compare
12 tasks
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.
Bloats the bundle size
I'm aware of the semantic difference between nullish coalescing and the
||-operator but I think for our use cases, replacing??with||should be fine.