This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Repository navigation
Add support for optional chaining within template literals - #586
Closed
brennenberkley wants to merge 2 commits into
Closed
brennenberkley wants to merge 2 commits into
brennenberkley wants to merge 2 commits into
Conversation
1 task done
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 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.
Description of the Change
obj?.propAlternate Designs
None
Benefits
Using conditional chaining will not break syntax highlighting as shown in #584
Possible Drawbacks
I did not add any specific category for
?, but that could be handled in another PRApplicable Issues
#584