Angular component interaction two-way binding approaches
I am new to Angular and trying to understand the possibilities.
To achieve 2-way binding between Angular components for interactions, I have come up with the following possibilities. Is it feasible to use options 5 and 6 as they are not mentioned in the angular documentation.
- Event binding + Interaction via child tag level template variable (allows access to child variables from parent template only, and not in component)
- Event binding + Interaction via @ViewChild() (this allows access to child variables from parent component)
- Via service
- Event Binding + Property binding
- Banana syntax approach (code mentioned below)
- ngModel
<childcomponent ([ipVar])="ParentVar">
angular asked Nov 2 '18 at 11:11
variablevariable
96221943
add a comment |
I am new to Angular and trying to understand the possibilities.
To achieve 2-way binding between Angular components for interactions, I have come up with the following possibilities. Is it feasible to use options 5 and 6 as they are not mentioned in the angular documentation.
- Event binding + Interaction via child tag level template variable (allows access to child variables from parent template only, and not in component)
- Event binding + Interaction via @ViewChild() (this allows access to child variables from parent component)
- Via service
- Event Binding + Property binding
- Banana syntax approach (code mentioned below)
- ngModel
<childcomponent ([ipVar])="ParentVar">asked Nov 2 '18 at 11:11
variablevariable
96221943
add a comment |
I am new to Angular and trying to understand the possibilities.
To achieve 2-way binding between Angular components for interactions, I have come up with the following possibilities. Is it feasible to use options 5 and 6 as they are not mentioned in the angular documentation.
- Event binding + Interaction via child tag level template variable (allows access to child variables from parent template only, and not in component)
- Event binding + Interaction via @ViewChild() (this allows access to child variables from parent component)
- Via service
- Event Binding + Property binding
- Banana syntax approach (code mentioned below)
- ngModel
<childcomponent ([ipVar])="ParentVar">asked Nov 2 '18 at 11:11
variablevariable
96221943
I am new to Angular and trying to understand the possibilities.
To achieve 2-way binding between Angular components for interactions, I have come up with the following possibilities. Is it feasible to use options 5 and 6 as they are not mentioned in the angular documentation.
- Event binding + Interaction via child tag level template variable (allows access to child variables from parent template only, and not in component)
- Event binding + Interaction via @ViewChild() (this allows access to child variables from parent component)
- Via service
- Event Binding + Property binding
- Banana syntax approach (code mentioned below)
- ngModel
<childcomponent ([ipVar])="ParentVar"> <childcomponent ([ipVar])="ParentVar"> <childcomponent ([ipVar])="ParentVar">asked Nov 2 '18 at 11:11
variablevariable
96221943
asked Nov 2 '18 at 11:11
variablevariable
96221943
edited Nov 23 '18 at 5:50
variable
asked Nov 2 '18 at 11:11
variablevariable
96221943
asked Nov 2 '18 at 11:11
variablevariable
96221943
asked Nov 2 '18 at 11:11
variablevariable
96221943
96221943
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In your child component you have to implement two-way binding interface like this:
private _ipVar: any;
get ipVar(): any {
return this._ipVar;
}
@Input()
set ipVar(value: any) {
if(this._ipVar === value) {
return;
}
this._ipVar = value;
this.ipVarChange.emit(this._ipVar);
}
@Output()
ipVarChange = new EventEmitter<any>();
It's mandatory to name @Output filed by adding word Change to @Input name.
So you can use it in your parent component temlate like this:
<childcomponent [(ipVar)]="ParentVar"></childcomponent>
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2fstackoverflow.com%2fquestions%2f53117507%2fangular-component-interaction-two-way-binding-approaches%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In your child component you have to implement two-way binding interface like this:
private _ipVar: any;
get ipVar(): any {
return this._ipVar;
}
@Input()
set ipVar(value: any) {
if(this._ipVar === value) {
return;
}
this._ipVar = value;
this.ipVarChange.emit(this._ipVar);
}
@Output()
ipVarChange = new EventEmitter<any>();
It's mandatory to name @Output filed by adding word Change to @Input name.
So you can use it in your parent component temlate like this:
<childcomponent [(ipVar)]="ParentVar"></childcomponent>
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
add a comment |
In your child component you have to implement two-way binding interface like this:
private _ipVar: any;
get ipVar(): any {
return this._ipVar;
}
@Input()
set ipVar(value: any) {
if(this._ipVar === value) {
return;
}
this._ipVar = value;
this.ipVarChange.emit(this._ipVar);
}
@Output()
ipVarChange = new EventEmitter<any>();
It's mandatory to name @Output filed by adding word Change to @Input name.
So you can use it in your parent component temlate like this:
<childcomponent [(ipVar)]="ParentVar"></childcomponent>
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
add a comment |
In your child component you have to implement two-way binding interface like this:
private _ipVar: any;
get ipVar(): any {
return this._ipVar;
}
@Input()
set ipVar(value: any) {
if(this._ipVar === value) {
return;
}
this._ipVar = value;
this.ipVarChange.emit(this._ipVar);
}
@Output()
ipVarChange = new EventEmitter<any>();
It's mandatory to name @Output filed by adding word Change to @Input name.
So you can use it in your parent component temlate like this:
<childcomponent [(ipVar)]="ParentVar"></childcomponent>
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
In your child component you have to implement two-way binding interface like this:
private _ipVar: any;
get ipVar(): any {
return this._ipVar;
}
@Input()
set ipVar(value: any) {
if(this._ipVar === value) {
return;
}
this._ipVar = value;
this.ipVarChange.emit(this._ipVar);
}
@Output()
ipVarChange = new EventEmitter<any>();
It's mandatory to name @Output filed by adding word Change to @Input name.
So you can use it in your parent component temlate like this:
<childcomponent [(ipVar)]="ParentVar"></childcomponent>
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
answered Nov 2 '18 at 11:35
Dmitriy SnitkoDmitriy Snitko
601313
601313
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53117507%2fangular-component-interaction-two-way-binding-approaches%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
