-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Component sendAction
doesn't handle attrs. + action
correctly
#11176
Comments
I reverted to Ember 1.12.0. Bug is gone. The implementation for |
sendAction
doesn't handle attrs. + action
correctlysendAction
doesn't handle attrs. + action
correctly
I attempted to replicate the scenario you described in this JSBin, but it properly triggers the route action. |
Ahh, so it appears that you are not passing the action name down as a string in the template, but rather as a bound property that resolves to a string (like |
Possibly related, I can't send actions to components since 1.13-beta.1: http://stackoverflow.com/questions/30274097/sending-actions-to-a-component-with-ember-js-1-13?noredirect=1#comment48650708_30274097 (isolated test cases included) |
Working through this now, I'll have a fix in an hour or two |
[BUGFIX beta] Handle mut cell action names. Fixes #11176
@mixonic thanks a lot. Assuming the bugs are/were related I tried it out but no dice with the testcase here: http://jsbin.com/gohovifedi/2/edit Any ideas? |
@oskarrough this issue was completely unrelated to #11192. |
I pass a route action name string to a component. That component will send that action when one of it's own actions is triggered. Refer to the example below.
Given the below implementation in Ember.1.13.0-Beta-1:
property_get.get(this, "attrs." + action)
will return an object of the following format:Since the result is an
Object
it fails the assertion.We can extract the value by changing the
actionName
assignment to:That's just a suggestion though, I'm not sure of the implications of the change.
The text was updated successfully, but these errors were encountered: