-
-
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
Positional params issue in contextual components #12625
Comments
I think I know what's happening. If I'm right, it would be a quick fix. I'm having dinner, I'll check later. |
This feature does not exist in 2.2, so it would be a |
Of course! My mistake. |
Serabe
added a commit
to Serabe/ember.js
that referenced
this issue
Nov 19, 2015
… syntax As reported in emberjs#12625, positional parameters were not being rendered correctly when using the dot syntax. A longer description on the cause of the problem has been added as a comment to `ember-htmlbars/lib/hooks/component.js` for future warning. Fix emberjs#12625
rwjblue
pushed a commit
that referenced
this issue
Nov 19, 2015
… syntax As reported in #12625, positional parameters were not being rendered correctly when using the dot syntax. A longer description on the cause of the problem has been added as a comment to `ember-htmlbars/lib/hooks/component.js` for future warning. Fix #12625 (cherry picked from commit a18490a)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An assertion is being triggered when attempting to use positional params with contextual components via the hash helper.
Imagine the following
If we attempt to instantiate
childComponent
directly, the assertion is triggered, if we instantiatechildComponent
using the component helper, everything works as expected. See below for examples:I've also created a couple of Twiddles, one showing the error and one showing it working when used with the component helper.
Working:
https://ember-twiddle.com/331b165b525660a2307d
Not Working:
https://ember-twiddle.com/cef32d9fc97b265e824b
The assertion being thrown is:
I discovered the issue on v2.3.0-beta.1 although I suspect the issue could also affect v2.2.0.
The text was updated successfully, but these errors were encountered: