-
Notifications
You must be signed in to change notification settings - Fork 79
Implement spread binding #57
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Conversation
really extensive 😄 |
Same |
I would love to see this implemented. |
I like the idea, but I think a |
Because the spread operator already exists for passing attributes, it seems tempting to use similar syntax for binding and even event handling. But I feel that semantically it doesn't really make sense. To give you an example where I am coming from, a common practice when you use destructuring assignment in JS you do so to create a new object with a new reference, to prevent mutation on the source object. ie: As much I like your suggestion of Some Pros:
|
This would be a nice feature to have. It helps us create more dynamic components and wrappers. Any updates on this? |
Any updates on this? It would be definitely a nice feature to have. |
I hit a snag where I could really make use of this feature. |
Rendered.