Can you make the video series of angular universal(SSR) to improve the performance. It would be really cool if you cover the performance and hosting and minimizing the bundle size of SSR application.
can you please make a video about best practices of angular application structure? How should we create, manage and use our libraries? what is the pros and cons?
Thanks for clear explanation, I have understood that exportAs enables access to directive instance. Can element allow more than on template reference in case I want access to both input and directive Can exportAs replace @Input and @Output communicate to directive
Hi! Yes, you can have multiple template references on the same element. Regarding replacing inputs and outputs I would not say that it can be replaced by it.
I think it is because, unlike ngModel, the FormControlName doesn’t „own“ the FormControl instance which represents the state of control, so there is nothing to read from that.
Level up your Angular skills with my advanced courses 🚀
bit.ly/advanced-angular-courses
Талант розглядати цікаві теми. Один з кращих каналів по Ангуляру!
Дякую 🙌🏻
You are the best, thank you, I will be very happy to see deep explanation of angular animations by you, thank you agin ❤
Can you make the video series of angular universal(SSR) to improve the performance. It would be really cool if you cover the performance and hosting and minimizing the bundle size of SSR application.
Thank you Dmytro for this new version of the video on exportAs.
The explanations are much clear and precise.
I hope it is really so :) Thank you!
Дякую, шикарне відео
🙌🏻
Thank for your explaination!
Thank you. Glad to hear that 🙂
Very clear explanation. I haven't used this property yet but it's good to understand the possible use cases.
Дякую! 👍
🙌🏻 you are welcome! Thanks for this comment.
can you please make a video about best practices of angular application structure? How should we create, manage and use our libraries? what is the pros and cons?
Excellent video!! Thank you so much..
Thanks for another useful video, Dmytro 😉
Very informative. Thanks buddy
I thought I missed some bonus time video, while saw it in subscription, but didn't see it in your channel 😂
It is actually good for you that you didn't see it because this one is more accurate 😉
Thanks for clear explanation, I have understood that exportAs enables access to directive instance.
Can element allow more than on template reference in case I want access to both input and directive
Can exportAs replace @Input and @Output communicate to directive
Hi! Yes, you can have multiple template references on the same element. Regarding replacing inputs and outputs I would not say that it can be replaced by it.
Please upload your previous video of this export as, which you have deleted. That was also very beautiful expression.
Thank you for the updated video :)
Thank you 😊
Thank you, as always
Дуже хороший приклад
Дякую 😊
why formControlName directive don't have exportAs variable ?
I think it is because, unlike ngModel, the FormControlName doesn’t „own“ the FormControl instance which represents the state of control, so there is nothing to read from that.
@@DecodedFrontend Due to that showing form controls validation errors will be little bit tough.
very cool video
so beautiful English!
Thank you (if it is not a touch of sarcasm 😅).
awesome ❤
Thanks 🤗
useful and shared
Було корисно😊
Радий це чути. Дякую! :)
:)
I see very useful and cool property. I personally dont know about this new property.
Actually, it is not a new one :) It exists quite a lot but it was used not so often