<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Component Interaction on Omid Farhang</title><link>https://omid.dev/tags/component-interaction/</link><description>Recent content in Component Interaction on Omid Farhang</description><generator>Hugo -- 0.152.2</generator><language>en-US</language><copyright>2025 Omid Farhang | All rights reserved.</copyright><lastBuildDate>Sun, 08 Sep 2024 12:56:55 +0330</lastBuildDate><atom:link href="https://omid.dev/tags/component-interaction/index.xml" rel="self" type="application/rss+xml"/><item><title>Unlocking the Power of Angular's `@ViewChild` and `@ContentChild`</title><link>https://omid.dev/2024/09/08/unlocking-the-power-of-angulars-viewchild-and-contentchild/</link><pubDate>Sun, 08 Sep 2024 12:56:55 +0330</pubDate><guid>https://omid.dev/2024/09/08/unlocking-the-power-of-angulars-viewchild-and-contentchild/</guid><description>&lt;p&gt;Angular&amp;rsquo;s &lt;code&gt;@ViewChild&lt;/code&gt; and &lt;code&gt;@ContentChild&lt;/code&gt; decorators provide a powerful way to interact with child components, DOM elements, and projected content within a component&amp;rsquo;s template. While they are often misunderstood or used interchangeably, each has its own specific purpose and use cases.&lt;/p&gt;
&lt;p&gt;In this comprehensive guide, we’ll dive deep into both decorators, understanding their differences, use cases, and best practices. Additionally, we’ll explore advanced techniques for leveraging them in various scenarios and edge cases, complete with sample code for hands-on understanding.&lt;/p&gt;</description></item></channel></rss>