Repository navigation
Ability to set attrs/properties on root element of a component #1009
Description
I have a <side-menu> component in 2.0.0-alpha.13. Currently, to set the open class on the side menu to show/hide it, I have to manually manipulate the dom element:
import {Component, Template, NgElement} from 'angular2/angular2';
@Component({
selector: 'side-menu'
})
@Template({
inline: `<div class="scroll-area">
<content></content>
</div>`
})
class SideMenu {
constructor(@NgElement() el: NgElement) {
this.element = el;
}
//drag logic ommitted...
setOpen(isOpen) {
this.isOpen = isOpen;
this.element.domElement.classList[isOpen ? 'add' : 'remove']('open');
}
}I'd like to be able to setup a [class.open]="isOpen" binding on my component's element instead of having to do this.
@mhevery suggested injecting @PropertySetter('class.open') setter: Function into the constructor, but that errors when used because the actual setter function tries to set domElement.class.open. And domElement.class does not exist.
Activity
[-]Allow setting of attributes/properties on root element of a component[/-][+]Setting of attributes/properties on root element of a component[/+][-]Setting of attributes/properties on root element of a component[/-][+]Setting of attrs/properties on root element of a component[/+][-]Setting of attrs/properties on root element of a component[/-][+]Ability to set attrs/properties on root element of a component[/+]ajoslin commentedon Mar 19, 2015
Duplicate of #1008
mhevery commentedon Mar 19, 2015
@pkozlowski-opensource both#1008 and #1009. I think that
@PropertySetter('a.b')should go through same code path as[a.b]. Since we already have[a.b]this should be straight forward.angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.