Repository navigation
Conversation
Updated the logic for preserveDestructuring option to default to true if not specified.
Collaborator
|
@vzaidman / @javache what's the status of this internally these days?
I'd be happy to see this transform turned off but I half recall some specific performance concerns (@tmikov?) |
This branch has not been deployed
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.
Summary:
The latest Hermes engine work well with destructuring syntax. I decided to checked perf. on
RN 0.88.x+ Samsung S10 and based on the result I don't see the reason to keep transforming destructuring syntax:Changelog:
[GENERAL] [BREAKING] - Turn off
@babel/plugin-transform-destructuringpluginTest Plan:
babel.config.jsto toggleunstable_preserveDestructuring: true/false