fix: index referring to scope?.[scopeName] being undefined #3047
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
loonskai
requested review from
StephenHaney,
vladmoroz,
lucasmotta and
hadihallak
as code owners
chaance
approved these changes
Sep 27, 2024
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.
Description
Adding an additional optional chaining operator for
scope?.[scopeName]?.[index]. We started seeingscope?.[scopeName]asundefinedafter switching to esbuild under specific conditions.Not sure whether such situation happens because a scope is not provided or there is incorrect scope composition. Adding an extra layer of safety ensures that both
scope?.[scopeName]andscope?.[scopeName]?.[index]are properly checked.