How to use Aura:Iteration index variable inside a placeholder?
up vote
1
down vote
favorite
I have a component which has a list of teams over which the aura:iteration is looping.
I want to use the placeholder attribute of lightning:input as such:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
But this gives the following result:
This works perfectly fine, if i only include the index in the merge expression:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
Can someone please help me out?
lightning-components lightning
add a comment |
up vote
1
down vote
favorite
I have a component which has a list of teams over which the aura:iteration is looping.
I want to use the placeholder attribute of lightning:input as such:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
But this gives the following result:
This works perfectly fine, if i only include the index in the merge expression:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
Can someone please help me out?
lightning-components lightning
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a component which has a list of teams over which the aura:iteration is looping.
I want to use the placeholder attribute of lightning:input as such:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
But this gives the following result:
This works perfectly fine, if i only include the index in the merge expression:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
Can someone please help me out?
lightning-components lightning
I have a component which has a list of teams over which the aura:iteration is looping.
I want to use the placeholder attribute of lightning:input as such:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
But this gives the following result:
This works perfectly fine, if i only include the index in the merge expression:
<aura:iteration items="{!v.dToPart.teams}" var="eachTeam" indexVar="index">
<div class="slds-col slds-size_4-of-12 " >
<lightning:input placeholder="{'Name of team '+ #index+1}" aura:id="dToPart" value="{!eachTeam.name}" required="true"/>
</div>
</aura:iteration>
Can someone please help me out?
lightning-components lightning
lightning-components lightning
asked 1 hour ago
Shridhar Puntambekar
416
416
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
Expressions need to start with # or ! to be recognized:
<lightning:input placeholder="{#'Name of team '+ (index+1)}" ... />
Note that the inner (
and )
are necessary to treat the index + 1
as arithmetic instead of string concatenation.
An expression is always in the form of {
, followed by #
or !
, followed by the expression to be evaluated, and finally ending in }
.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Expressions need to start with # or ! to be recognized:
<lightning:input placeholder="{#'Name of team '+ (index+1)}" ... />
Note that the inner (
and )
are necessary to treat the index + 1
as arithmetic instead of string concatenation.
An expression is always in the form of {
, followed by #
or !
, followed by the expression to be evaluated, and finally ending in }
.
add a comment |
up vote
2
down vote
Expressions need to start with # or ! to be recognized:
<lightning:input placeholder="{#'Name of team '+ (index+1)}" ... />
Note that the inner (
and )
are necessary to treat the index + 1
as arithmetic instead of string concatenation.
An expression is always in the form of {
, followed by #
or !
, followed by the expression to be evaluated, and finally ending in }
.
add a comment |
up vote
2
down vote
up vote
2
down vote
Expressions need to start with # or ! to be recognized:
<lightning:input placeholder="{#'Name of team '+ (index+1)}" ... />
Note that the inner (
and )
are necessary to treat the index + 1
as arithmetic instead of string concatenation.
An expression is always in the form of {
, followed by #
or !
, followed by the expression to be evaluated, and finally ending in }
.
Expressions need to start with # or ! to be recognized:
<lightning:input placeholder="{#'Name of team '+ (index+1)}" ... />
Note that the inner (
and )
are necessary to treat the index + 1
as arithmetic instead of string concatenation.
An expression is always in the form of {
, followed by #
or !
, followed by the expression to be evaluated, and finally ending in }
.
answered 1 hour ago
sfdcfox
243k10185413
243k10185413
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f241938%2fhow-to-use-auraiteration-index-variable-inside-a-placeholder%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown