The <FroalaEditor /> component largely depends on interaction with the attached element to initialize the Froala Editor. Technically ember now allows this access by using a modifier. Most of the <FroalaEditor /> code could be moved to a modifier class definition. However, there are some downsides that the component version guards against (mainly ensuring @content is passed in and not used as block content <FroalaEditor>{{this.content}}</FroalaEditor>ember-render-modifiers to gain access to the element. At minimum, I would say both (component and modifier) would be provided by the addon if we do move to a modifier. An alternate and more custom solution is to create a custom modifier manager too, to avoid a dependency on ember-modifier.
The
<FroalaEditor />component largely depends on interaction with the attachedelementto initialize the Froala Editor. Technically ember now allows this access by using a modifier. Most of the<FroalaEditor />code could be moved to a modifier class definition. However, there are some downsides that the component version guards against (mainly ensuring@contentis passed in and not used as block content<FroalaEditor>{{this.content}}</FroalaEditor>ember-render-modifiersto gain access to theelement. At minimum, I would say both (component and modifier) would be provided by the addon if we do move to a modifier. An alternate and more custom solution is to create a custom modifier manager too, to avoid a dependency onember-modifier.