<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Amit Yadav</title>
    <description>The latest articles on DEV Community by Amit Yadav (@raoamit47).</description>
    <link>https://dev.to/raoamit47</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2305579%2F70989292-7366-43ca-abd2-0835322749c9.JPEG</url>
      <title>DEV Community: Amit Yadav</title>
      <link>https://dev.to/raoamit47</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/raoamit47"/>
    <language>en</language>
    <item>
      <title>Building an Angular CRUD App with a Go API</title>
      <dc:creator>Amit Yadav</dc:creator>
      <pubDate>Mon, 04 Nov 2024 06:40:43 +0000</pubDate>
      <link>https://dev.to/raoamit47/building-an-angular-crud-app-with-a-go-api-3e46</link>
      <guid>https://dev.to/raoamit47/building-an-angular-crud-app-with-a-go-api-3e46</guid>
      <description>&lt;p&gt;CRUD operations (Create, Read, Update, Delete) are the backbone of most web applications. In this tutorial, we’ll show you how to build a CRUD app with Angular on the front end and a GoAPI on the back end, resulting in a fully integrated and efficient full-stack solution.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://dev.to/stackpuz/building-an-angular-crud-app-with-a-go-api-4m80"&gt;https://dev.to/stackpuz/building-an-angular-crud-app-with-a-go-api-4m80&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In conclusion, we have learned how to create a basic Angular project with components, views, and routing, while setting up an API using the Gin framework as the backend. By utilizing GORM for database operations, we've successfully built a dynamic front-end that seamlessly integrates with a powerful and efficient backend. This combination forms a solid foundation for developing modern, full-stack web applications.&lt;/p&gt;

&lt;p&gt;Source code: &lt;a href="https://github.com/stackpuz/Example-CRUD-Angular-18-Go" rel="noopener noreferrer"&gt;https://github.com/stackpuz/Example-CRUD-Angular-18-Go&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Create an Angular CRUD App in Minutes: &lt;a href="https://stackpuz.com" rel="noopener noreferrer"&gt;https://stackpuz.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>angular</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Using Conditional Properties in TypeScript: A Practical Example</title>
      <dc:creator>Amit Yadav</dc:creator>
      <pubDate>Wed, 30 Oct 2024 06:40:21 +0000</pubDate>
      <link>https://dev.to/raoamit47/using-conditional-properties-in-typescript-a-practical-example-3p0e</link>
      <guid>https://dev.to/raoamit47/using-conditional-properties-in-typescript-a-practical-example-3p0e</guid>
      <description>&lt;p&gt;In TypeScript, conditional properties allow us to create flexible and type-safe interfaces that adapt based on certain conditions. This is particularly useful when dealing with complex data structures where certain properties should only be present under specific circumstances. In this blog post, we’ll explore how to use conditional properties with a practical example involving reward groups.&lt;/p&gt;

&lt;p&gt;Imagine we have a system that manages different types of rewards. Each reward can be of a specific type, such as “FINANCE” or “SHIPPING”.&lt;/p&gt;

&lt;p&gt;Depending on the reward type, certain attributes should be included or excluded. For instance, financial rewards should include financial attributes, while shipping rewards should include shipping attributes. Additionally, we want to ensure that certain attributes are only included based on the reward type and reward on conditions.&lt;/p&gt;

&lt;p&gt;Conditional Types:&lt;br&gt;
We use a union of three types to handle the conditional properties.&lt;/p&gt;

&lt;p&gt;When rewardType is “FINANCE” and rewardOn is “Finance”, financeAttributes is required,&lt;br&gt;
and rewardAttributes and shippingAttributes are not allowed.&lt;/p&gt;

&lt;p&gt;When rewardType is “SHIPPING” and rewardOn is not “Finance”, shippingAttributes is required, and financeAttributes is not allowed, but rewardAttributes is included.&lt;/p&gt;

&lt;p&gt;For any other rewardType and rewardOn not being “Finance”, rewardAttributes is included, but neither financeAttributes nor shippingAttributes are included.&lt;/p&gt;

</description>
      <category>typescript</category>
    </item>
  </channel>
</rss>
