-
Notifications
You must be signed in to change notification settings - Fork 26
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
Partial Incompatibility with Ember 2.10 #43
Comments
https://github.com/ciena-blueplanet/ember-block-slots/blob/master/addon/helpers/block-params.js#L27-L31 is likely the cause Introduced by emberjs/ember.js#14244 |
jasonmit
added a commit
to jasonmit/ember-block-slots
that referenced
this issue
Dec 8, 2016
Awesome root cause analysis and thanks a ton for the PR! |
sglanzer-deprecated
pushed a commit
that referenced
this issue
Dec 8, 2016
Closed via #44 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@thoov and I came across a case where
ember-block-slots
is not compatible with Ember 2.10.0. It seems that yielding a set of arguments to a block slot throughblock-params
, when once of those params is ahash
, causes the following issue on browsers that do not have a nativeWeakMap
implementation (yeah, it took a while to get to the bottom of this 😉 )I created a demo repo here that reproduces the issue. Basically, run the tests in Phantom and you'll see a failure, but in Chrome you will not. Just running
ember test
will show a message that isn't helpful, an error about an assertion that is just a symptom of the real problem. If you doember test --serve
you'll see both that error, plus an additional message about the "real" one.Output from
ember test
Output from
ember test --serve
The text was updated successfully, but these errors were encountered: