This repository was archived by the owner on Aug 4, 2021. It is now read-only.
handle Literal types as ObjectPattern keys#27
Merged
guybedford merged 3 commits intorollup:masterfrom May 6, 2018
Merged
Conversation
Contributor
|
Thanks for the PR here. Could you please add a test for the ObjectPattern case here? |
Contributor
Author
|
Sure! |
Contributor
|
Thanks for the quick fix Do you think we could include a nested case like: ({ a: { b: c } } = { a: { b: 'b' } });just to be sure the destructuring plays out right? |
Contributor
Author
|
Hi @guybedford, I am sorry for the delay. I added the case |
Contributor
|
@edoardocavazza sure it would be great to create an issue for that. This looks great to me, thanks again for the PR. |
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.
fixes #25
added
Literalto extractors