-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Add failing test for @content-helper lookup #105
Conversation
…r) are resolved fine
Ok. Now fix it ;) |
Looks good to me. @stefanpenner - Thoughts? |
can someone describe concisely the use of |
@stefanpenner - This |
I wrote a little more of a rambling explanation in #101 (comment) and emberjs/ember.js#11987. |
@rwjblue thanks for the links, let me read the backchat. |
@@ -57,6 +57,10 @@ define("ember/resolver", | |||
var prefix, type, name; | |||
var fullNameParts = fullName.split('@'); | |||
|
|||
if (/.*:@.*/.test(fullName)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- lets leave a comment here describing why this is needed
- it seems like the above split
fullName.split('@');
(on line 58) is not needed if we hit this branch, this should be cleaned up
@stefanpenner Is the comment and changes I made sufficient? |
@tim-evans yup, LG. @rwjblue you are more familiar with that part of HTMLBars, so merge & release when you are comfortable with it. |
OK, I did a bit more digging into what was happening and I'd prefer to specifically blacklist @tim-evans - Can you tweak (hopefully for the last time) to just compare |
Can't this change be made in htmlbars instead? @content-helper is an internal that shouldn't be leaking out... |
…future release of htmlbars will remove this helper
@rwjblue done. |
Beautiful! |
Add failing test for @content-helper lookup
Ok rwjblue convinced me this is good |
Could we get a release on this? ember-document-title doesn't work on 1.13.X because of this. :( I checked on 1.13.8 and it no longer throws errors when calling |
releasing now. |
|
@tim-evans let me know if that does the trick, sorry for letting this linger. |
Sadly, no. I'll come up with an ember-twiddle to report this. |
@tim-evans ah so an additional bug in the resolver? |
I'm not sure. |
@tim-evans can you open a new issue, describing what is expected. I would love to dive in later this morning :) |
Related to #101