My problem is related to placing the same ponent with different parameters on the same page. In this case it is a ponent containing a chart from a third party Javascript library (D3JS) which needs an HTML id
attribute to locate and modify the ponent's HTML contents.
Now this id
attribute should contain a unique string for each chart placed on the page, and if I directly set it as a string from the parent ponent it works just fine:
<my-chart id="gaugeChart0"></my-chart>
The reason it works is I guess, because the id
attribute exists right at ponent creation time and whatever code is trying to access it can do that right away.
However this chart is in turn embedded into a bootstrap 4 card layout, like so:
<div class="row">
<div class="col-6">
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart id="gaugeChart0"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
</div>
<div class="col-6">
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart id="gaugeChart1"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
</div>
</div>
Now to make it more convenient (and to easily bind to click events to the whole block etc.) I would like to extract the whole part beginning with <div class="card">
into a new ponent.
Let's say I call this new ponent WidgetContainerComponent which contains the chart as well as the bootstrap card layout including the other widgets defined there.
The resulting code when using this wrapper ponent would be:
<div class="row">
<div class="col-6">
<widget-container chartId="gaugeChart0"></widget-container>
</div>
<div class="col-6">
<widget-container chartId="gaugeChart1"></widget-container>
</div>
</div>
In order for that to work the WidgetContainerComponent has an input field
@Input() chartId: string;
that can be set.
What I want to do then is to set the id
attribute of the MyChartComponent to the string that has been set to chartId
:
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart [id]="chartId"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
But this does not work, as angular adds a prefix to the id
attribute which results in something like ng-reflect-id
.
I also tried setting the attribute with [attr.id]
as described here and here:
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart [attr.id]="chartId"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
This results in the MyChartComponent having a straight id
attribute, but it seems to be only added at a later stage within the lifecycle of the ponent.
I also tried to initialize the chart within the MyChartComponent only in ngOnInit
and ngAfterContentInit
, but this does not work as well.
Any suggestions or ideas are very wele!
My problem is related to placing the same ponent with different parameters on the same page. In this case it is a ponent containing a chart from a third party Javascript library (D3JS) which needs an HTML id
attribute to locate and modify the ponent's HTML contents.
Now this id
attribute should contain a unique string for each chart placed on the page, and if I directly set it as a string from the parent ponent it works just fine:
<my-chart id="gaugeChart0"></my-chart>
The reason it works is I guess, because the id
attribute exists right at ponent creation time and whatever code is trying to access it can do that right away.
However this chart is in turn embedded into a bootstrap 4 card layout, like so:
<div class="row">
<div class="col-6">
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart id="gaugeChart0"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
</div>
<div class="col-6">
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart id="gaugeChart1"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
</div>
</div>
Now to make it more convenient (and to easily bind to click events to the whole block etc.) I would like to extract the whole part beginning with <div class="card">
into a new ponent.
Let's say I call this new ponent WidgetContainerComponent which contains the chart as well as the bootstrap card layout including the other widgets defined there.
The resulting code when using this wrapper ponent would be:
<div class="row">
<div class="col-6">
<widget-container chartId="gaugeChart0"></widget-container>
</div>
<div class="col-6">
<widget-container chartId="gaugeChart1"></widget-container>
</div>
</div>
In order for that to work the WidgetContainerComponent has an input field
@Input() chartId: string;
that can be set.
What I want to do then is to set the id
attribute of the MyChartComponent to the string that has been set to chartId
:
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart [id]="chartId"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
But this does not work, as angular adds a prefix to the id
attribute which results in something like ng-reflect-id
.
I also tried setting the attribute with [attr.id]
as described here and here:
<div class="card">
<div class="card-body">
<div class="row">
<div class="col-5">
<my-chart [attr.id]="chartId"></my-chart>
</div>
<div class="col-7">
... Some other widgets ...
</div>
</div>
</div>
</div>
This results in the MyChartComponent having a straight id
attribute, but it seems to be only added at a later stage within the lifecycle of the ponent.
I also tried to initialize the chart within the MyChartComponent only in ngOnInit
and ngAfterContentInit
, but this does not work as well.
Any suggestions or ideas are very wele!
Share Improve this question edited Oct 21, 2018 at 15:44 aegger asked Aug 20, 2018 at 19:21 aeggeraegger 4601 gold badge6 silver badges15 bronze badges 2- < div id="{{myvariable}}" > – Eliseo Commented Aug 20, 2018 at 19:32
-
Hi, you mean writing
<my-chart id="{{chartId}}"></my-chart>
instead of<my-chart [id]="chartId"></my-chart>
? I already tried this before, also in this case theid
attribute name gets prefixed with anng-reflect-
string which results in ang-reflect-id
attribute which is not recognized as an HTML id attribute. I think however that I already figured it out, I will post an answer later. – aegger Commented Aug 21, 2018 at 11:15
1 Answer
Reset to default 12So I found a solution to this problem. The problem was twofold:
The first problem was related to the requirement of having a genuine
id
attribute in contrast to the attribute name prefixed withng-reflect-
by angular.What I didn't know is that from Angular 4, this prefix gets added to any attribute which is declared as an
@Input
variable for the ponent in development mode (for an in-depth explanation see this post).The solution to this problem was to write
[attr.id]=chartId
instead of[id]=chartId
. The reason is that in this case I needed to set an HTML Attribute, however using the square brackets notation I created a Property Binding. In order to dynamically set an HTML Attribute via the property binding syntax you have to add the prefixattr.
to the attribute's name.For a good overview regarding all valid binding syntaxes see the Angular Docs. Specifically to review how to do attribute binding see this section.
The second problem was that I tried to access the
id
attribute of the ponent when it has not yet been created. This problem is related to the lifecycle hooks of Angular, where there are different stages. For a good overview of Angular's lifecycle hooks, see this page.Because I didn't know it myself in detail, I will elaborate it here shortly.
Angular es with a fixed set of lifecycle hooks which are called each time a ponent is set up and are also called in a predefined order. The hooks are defined as follows:
- constructor
- ngOnChanges
- ngOnInit
- ngDoCheck
- ngAfterContentInit
- ngAfterContentChecked
- ngAfterViewInit
- ngAfterViewChecked
- ngOnDestroy
_
Important to note is that elements created or prepared in one step can only be accessed in any of the subsequent steps. In my case I put all the code for the initialization of the chart into the
ngAfterContentInit
hook, however the ponent is only fully loaded whenngAfterViewInit
is called.Finally the solution was to put the pre-initialization code into the constructor and to place the chart initialization code into the
ngAfterViewInit
method. At this stage theid
attribute had been created properly and could be accessed by the chart.