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
[Glimmer2] tests for html-safe and render #13845
Conversation
@chadhietala - This is good to me. Can you make https://github.com/emberjs/ember.js/blob/master/packages/ember-htmlbars/lib/utils/string.js a symlink to the |
@@ -0,0 +1 @@ | |||
../../../ember-htmlbars/lib/utils/string.js |
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.
I think this should go the other way since in the long term we are going to rm -rf packages/ember-htmlbars
.
Overall this look good (one comment/tweak), can you confirm that |
What I ended up doing is moving the string module into |
Ember.HTMLBars = { SafeString }; | ||
} | ||
|
||
if (Ember.HandlerBars) { |
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.
Should be Ember.Handlebars
(a few places below are typo'ed too).
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.
Can you also move these Ember.Handlebars
exports to ember-templates/compat
?
Had to do some reorg and deletion of some similar work. Also moved the action test to #13850. |
EmberHTMLBars.template = EmberHandlebars.template = template; | ||
EmberHTMLBarsUtils.escapeExpression = EmberHandleBarsUtils.escapeExpression = escapeExpression; |
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.
I do not believe that we ever exposed this previously on Ember.HTMLBars
, can you confirm and if we haven't fixup?
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.
Fixed.
Maintain our own safestring and escapeexpression for now
LGTM |
/cc @krisselden @rwjblue
Pretty sure we want to just use the SafeString from HandleBars, however it is unclear how we should import it sense it was a proxy import in HTMLBars.