fix: Simplified level assignment logic in BrowserConsole #7329
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.
Description
I’ve updated the logic in the
BrowserConsole
function that handles thelevel
property. Previously, there was a redundant check foropts
in the conditional expression. Since we are already checking for the existence ofopts?.level
, it's unnecessary to verifyopts
again.I’ve simplified the assignment to use the nullish coalescing operator (
??
), which directly assigns the value ofopts.level
if it exists, or defaults to"info"
if it doesn't ;)