-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Destructure of function parameters - Refactoring #24827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
But shouldn't it be const calllback = event => {
const target = event.target;
// code with used target
} to const calllback = ({target}) => {
// code with used target
} |
@Shinigami92 Of course (May optionally be |
There's a big difference between your two examples though. In the first one |
@jcready Oh, I do not know why it seemed to me that it was different. Actually, you can do it somehow? Or are there any standard plans for this? |
Hi folks. |
@Kingwl What about function parameter destructure? And it looks like it works in one direction. |
Well, It's good to take a try. |
to
Same in the opposite direction and with a more complex and deep destructure and function content.
The text was updated successfully, but these errors were encountered: