Thank you so much. I think I've found a good Angular tutorial TH-cam channel. Before watching this video, I didn't have an idea about transferring data between unrelated components. Now, it's clear to me. From this video, I understand how to communicate with unrelated components using event emitters and subjects.
Still it does not explain why using an Subject over an Event emitter, having to know both concepts is good, but its way more important to know when to use one over the other.
now i am clear with subjects... provide same like this for the observables and which is the best to use in projects i want to using a service... if already have please share the video link...thanks
I just want to know if we don't have any click function to trigger the event from service then how we can trigger that method ? What if I just need only the value in another component without any button click or anything ..
The simple thing to understand here is that...what is going on in one component is not known to another component. If you want to pass a value from one component to another...the another component has to know that something has changed. For that we need to notify that component. To do that, we will have to emit some event. This event need not to be a click event, it can be any user defined event as well.
HI thanks for the explanation. My data being passed is little complicated, so I am using 'any' type definitions in the methods. I see an error subscribe does not exist on type '(data: any) => void'. Do you have any idea where I might be going wrong?
Subject is an observable which makes component comunication easier. It has nothing to do with events or EventEmitter. But, we can use it pass value from one component to another which are not related. But, if we don't have subject and want to communicate between two components which are not related, we need to use the concept of property binding and event binding and combine these concepts to achieve it.
Thank you so much. I think I've found a good Angular tutorial TH-cam channel. Before watching this video, I didn't have an idea about transferring data between unrelated components. Now, it's clear to me. From this video, I understand how to communicate with unrelated components using event emitters and subjects.
The way you teach us is just remarkable. Sometimes are confused that is we really learn Angular from TH-cam or a paid Udemy course. Kudos to you sir.
Your explanation was clear as water, thank you!!!
Excellent. This is what exactly I wanted. Please don't stop posting videos on TH-cam.
Best tutorial ever on angular
Thanks a lot, this has helped me big time with the project Im currently working on👍👍
Great Thanks Very Clear Tutorial About Subject...!
This was an amazing explanation. Thank you!!!
Are there any cases where use of Subject is recommended over EventEmitter?
Excellent knowledge
I have 5 years of experience
Even though I appreciate you
Thank you sir for uploading value your video very helpful.
Excellent! Learnt a lot. Thank you
I love the way you make it so easy!!
That was an excellent explanation !!
Very Nice explanation
Nicely explained, thank you.
Nice description, Do you have a repos for the same?
thank you for this useful tutorial
Still it does not explain why using an Subject over an Event emitter, having to know both concepts is good, but its way more important to know when to use one over the other.
now i am clear with subjects... provide same like this for the observables and which is the best to use in projects i want to using a service... if already have please share the video link...thanks
great explaination
Good one. Can you please add different unit test topics in Angular.
I have planned to do it at the end of this course.
@@procademy Thanks a lot 🙂
You're amazing. Thank you.
Very nice. Thank you
I just want to know if we don't have any click function to trigger the event from service then how we can trigger that method ? What if I just need only the value in another component without any button click or anything ..
The simple thing to understand here is that...what is going on in one component is not known to another component.
If you want to pass a value from one component to another...the another component has to know that something has changed. For that we need to notify that component. To do that, we will have to emit some event.
This event need not to be a click event, it can be any user defined event as well.
Great work. thank you
Let's say there is no button and I want to achieve same component interaction..how do we achieve it?
HI thanks for the explanation. My data being passed is little complicated, so I am using 'any' type definitions in the methods. I see an error subscribe does not exist on type '(data: any) => void'. Do you have any idea where I might be going wrong?
God bless you!
How your ngOnIt method gets called when you enter text?
If the two components were children of the same parent, should I still use subject?
How simple is that. Try to do the same in redux or vuex.
what is the difference between Subject and EventEmitter ?
Subject is an observable which makes component comunication easier. It has nothing to do with events or EventEmitter. But, we can use it pass value from one component to another which are not related.
But, if we don't have subject and want to communicate between two components which are not related, we need to use the concept of property binding and event binding and combine these concepts to achieve it.
@@procademy Thanks , it is clear
Great vídeo!
so why using subject instead of eventemitter? i don't get it
what is difference between eventemitter vs Obsevable?
Hi, could you discuss Subject a bit more? The official explanation is not too clear. Thank you
Waiting
13 dk services + 3 dk subject = Subjects in RxJs
thanks!
Please update response from below queries
Thanks can you please share code in github ?
Here is the github link to download the source code: github.com/manojjha86/complete-angular-13-course.git
@@procademy Thanks 😃😃
@@procademy Thank you so much sir for this GitHub link.