Question

108

Angular Component: no template replace option?

rated 0 times [ 112] [ 4] / answers: 1 / hits: 29931 / 8 Years ago, tue, february 9, 2016, 12:00:00

It looks like there is no replace option in new AngularJS 1.5 Component concept (like it was for directives).

What would you suggest if I want to have table row <TR> element as component? Is it not possible in terms of valid HTML?

Real example: mailBox component has mail components inside. By markup mail-box-component is table, and mail-box is tr.

<mail-box>

    <mail ng-repeat=mail in $ctrl.mails mail=mail></mail>

<mail-box>

UPD: related discussion about directives - Why is replace deprecated in AngularJS?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

yaquelina

Add To Favorites

Follow

Total Points: 517

Total Questions: 101

Total Answers: 96

Location: Egypt

Member since Tue, Jul 6, 2021

3 Years ago

yaquelina questions

1 Unable to access process variable in Vue3JS Vite project

Sun, Feb 13, 22, 00:00, 2 Years ago

1 How to return an array of unique objects based on the id of the object in es6?

Mon, Dec 27, 21, 00:00, 2 Years ago

1 How to run nodemon + forever in the background

Tue, Jun 2, 20, 00:00, 4 Years ago

1 How to remove warning in React native

Sun, Mar 8, 20, 00:00, 4 Years ago

1 Angular 9 - You must pass in a NgModule or NgModuleFactory to be bootstrapped

Fri, Feb 21, 20, 00:00, 4 Years ago

View All

answered 8 Years ago declanm · Accepted Answer

This is not possible the-angular-way anymore since the replace: true flag has been deprecated

Why is replace deprecated in AngularJS?

the replace: true flag had come up with more problems than solutions which is why it was removed.
therefore you can not build directives in such a way anymore and provide valid table-tr-td markup.

However, there are two reasons why this is not as bad as it looks:

you can do everything you want to do without table, tr, td, etc.
just using elements like div, span, etc. and some css on it

web-components (and directives were a first attempt to simulate
them) are not meant to represent such small fragments of the markup.
they are more thought of as a fully functional component actually
doing something. so whatever you want to do with your tr that you
think it's worth building an element-directive around it, it
probably isnt.

Maybe, what you can do is using an attribute-directive instead:

<tr my-mail-directive></tr>

and your my-mail-directive does the magic on the tr element