<?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>Forem: Rizk Ussef</title>
    <description>The latest articles on Forem by Rizk Ussef (@rizk_ussef).</description>
    <link>https://forem.com/rizk_ussef</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%2F3376128%2Fc711ee75-40ee-4073-aa66-9a4a4858ecdc.jpg</url>
      <title>Forem: Rizk Ussef</title>
      <link>https://forem.com/rizk_ussef</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/rizk_ussef"/>
    <language>en</language>
    <item>
      <title>🚀Laravel Core CRUD Package: Clean Architecture with Laravel Core CRUD</title>
      <dc:creator>Rizk Ussef</dc:creator>
      <pubDate>Fri, 27 Feb 2026 20:22:17 +0000</pubDate>
      <link>https://forem.com/rizk_ussef/laravel-core-crud-package-clean-architecture-with-laravel-core-crud-3h4d</link>
      <guid>https://forem.com/rizk_ussef/laravel-core-crud-package-clean-architecture-with-laravel-core-crud-3h4d</guid>
      <description>&lt;p&gt;🚀 Tired of rewriting CRUD logic in every Laravel project?&lt;/p&gt;

&lt;p&gt;After building countless APIs, I got fed up with repeating filtering, eager loading, pagination, and resource handling.&lt;br&gt;
So I built Laravel Core CRUD — a reusable package that automates the boring parts while keeping your architecture clean and scalable.&lt;/p&gt;

&lt;p&gt;⚡ Key Features:&lt;br&gt;
-Ultra-Thin Controllers: Just extend CoreCrudController and define your Service in constrain(). No more fat controllers.&lt;br&gt;
-Smart Auto-Resolution: Models, Resources and Requests are automatically handled.&lt;br&gt;
-Advanced Filtering: =,!=, LIKE, BETWEEN, IN, Date, NULL checks.&lt;br&gt;
-Dynamic Eager Loading: Frontend requests only the relationships it needs.&lt;br&gt;
-Consistent API: Standardized JSON responses and pagination.&lt;/p&gt;

&lt;p&gt;🏗 Architecture&lt;br&gt;
-UserController ➡ CoreCrudController → defines UserService in constrain()&lt;br&gt;
-UserService ➡ CoreCrudService → handles queries, filtering, pagination, relationships&lt;br&gt;
-UserResource → auto-resolved&lt;br&gt;
-UserRequest → auto-resolved&lt;br&gt;
-User → Eloquent model&lt;br&gt;
Everything is auto-resolved, keeping your controllers ultra-thin and your code DRY, maintainable, and professional.&lt;/p&gt;

&lt;p&gt;📦 Install via Composer:&lt;br&gt;
composer require rizkussef/laravel-core-crud&lt;/p&gt;

&lt;p&gt;📌 Check it out:&lt;br&gt;
Packagist: &lt;a href="https://lnkd.in/dSJhKxJf" rel="noopener noreferrer"&gt;https://lnkd.in/dSJhKxJf&lt;/a&gt;&lt;br&gt;
GitHub: &lt;a href="https://lnkd.in/dX7q7xPk" rel="noopener noreferrer"&gt;https://lnkd.in/dX7q7xPk&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F63wl2nquoako2zejoeeg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F63wl2nquoako2zejoeeg.png" alt=" " width="800" height="428"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>laravel</category>
      <category>api</category>
      <category>backend</category>
    </item>
    <item>
      <title>Are you tired of API response naming conflicts between Front-End &amp; Back-End?</title>
      <dc:creator>Rizk Ussef</dc:creator>
      <pubDate>Tue, 22 Jul 2025 16:06:10 +0000</pubDate>
      <link>https://forem.com/rizk_ussef/are-you-tired-of-api-response-naming-conflicts-between-front-end-back-end-1f79</link>
      <guid>https://forem.com/rizk_ussef/are-you-tired-of-api-response-naming-conflicts-between-front-end-back-end-1f79</guid>
      <description>&lt;p&gt;🚀 Are you tired of API response naming conflicts between Front-End &amp;amp; Back-End?&lt;/p&gt;

&lt;p&gt;Here’s the common problem:&lt;br&gt;&lt;br&gt;
✔ Back-End returns snake_case.&lt;br&gt;&lt;br&gt;
✔ Front-End wants camelCase.&lt;br&gt;&lt;br&gt;
❌ Result? Wasted time mapping keys manually.&lt;/p&gt;

&lt;p&gt;👨‍💻 I solved this with a Laravel Package that does all the work automatically!&lt;br&gt;
🐍🔁🐫 Laravel Snake-to-Camel Case Package&lt;br&gt;
📦 Features: &lt;br&gt;
✅ Two Middlewares:&lt;br&gt;&lt;br&gt;
1️⃣ Convert API Responses → camelCase.&lt;br&gt;&lt;br&gt;
2️⃣ Convert Form Requests → snake_case.&lt;br&gt;&lt;br&gt;
✅ Super easy: Just install it (no manual provider registration).&lt;br&gt;&lt;br&gt;
✅ Configurable: Apply to API, Web, or both.&lt;br&gt;&lt;br&gt;
✅ Choose: Response only or Request + Response.&lt;/p&gt;

&lt;p&gt;📌 Example config:&lt;/p&gt;

&lt;p&gt;'apply_to' =&amp;gt; 'all',&lt;br&gt;
'convert_request' =&amp;gt; true,&lt;br&gt;
'convert_response' =&amp;gt; true,&lt;/p&gt;

&lt;p&gt;🎯 Result:&lt;br&gt;
✅ No conflicts.&lt;br&gt;&lt;br&gt;
✅ Faster integration.&lt;br&gt;&lt;br&gt;
✅ Cleaner code.&lt;/p&gt;

&lt;p&gt;👉 &lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fspowfkc1su8s774ggx5k.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fspowfkc1su8s774ggx5k.png" alt=" " width="800" height="367"&gt;&lt;/a&gt;&lt;br&gt;
Check it out here:&lt;br&gt;
 &lt;a href="https://packagist.org/packages/rizkussef/laravel-snake-to-camel-case" rel="noopener noreferrer"&gt;https://packagist.org/packages/rizkussef/laravel-snake-to-camel-case&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>api</category>
      <category>php</category>
      <category>backend</category>
    </item>
  </channel>
</rss>
