DEV Community: Manjeet Singh

Laravel AI SDK Guide 2026

Manjeet Singh — Mon, 09 Feb 2026 13:01:06 +0000

Hey Laravel folks! Picture this: Laracon India 2026, Ahmedabad buzzing with energy, Taylor Otwell on stage, and boom — the official…

Continue reading on Medium »

My 8 Years in Dev: The Mindset and Practices That Make You a Better Developer

Manjeet Singh — Wed, 03 Dec 2025 12:32:10 +0000

After 8 years writing code, breaking things, learning from mistakes, and building serious products, one truth stands out: being a “good…

Continue reading on Medium »

Trait or Builder? The Complete Guide Every Laravel Developer Should Read

Manjeet Singh — Mon, 01 Dec 2025 13:02:18 +0000

Ever wondered whether you should reach for a Trait or build a Custom Eloquent Builder in your next Laravel project? You’re not alone! With Laravel pushing forward in 2025 and PHP 8.3+ powering our apps, writing maintainable, readable code is more crucial than ever. In this deep dive, I’ll break down Traits vs Builders for Laravel, tackle common developer pain points, and guide you to the best solution for real-world projects.

If you want cleaner code and more expressive queries, this post is for you. Drop a comment with your experience — what’s your go-to? Let’s boost your Laravel skills together!

Why This Topic Matters

Laravel developers, whether beginners or pros, are constantly balancing speed, scalability, and developer happiness. As Laravel every new version brings new features and stricter PHP standards, organizing business logic and query code is a hot topic in the community.

Think about it for a second: You want DRY, testable code — but maybe your models are stuffed with methods, or your query logic is scattered in Traits, controllers, or services. That’s where the Trait vs Builder debate gets real. The choices you make now can save hours (or cause headaches) later.

Let’s explore, clarify, and give you concrete, actionable advice. I’m
Coder Manjeet
— join me for a personal, community-driven deep dive!

What is a Trait in Laravel?

A Trait is a reusable set of methods in PHP, letting you share logic between different classes. In Laravel, traits are often used to:

Add query scopes to models (ActiveScope, PublishedScope)
Share event logic (like model observers)
Bundle helpers or utility functions

Example: Adding a reusable scope

trait HasActiveScope {
    public function scopeActive($query) {
        return $query->where('active', true);
    }
}

class User extends Model {
    use HasActiveScope;
}

class Post extends Model {
    use HasActiveScope;
}

The beauty: You can add active() to any model instantly.
But beware: Piling on too many traits clutters your model, and logic can get messy if traits start doing more than their original job.

What is a Custom Eloquent Builder?

A Custom Eloquent Builder is a class extending Laravel’s Builder, designed for powerful, expressive query logic. Want to clean up your models and centralize queries? Builder is your best friend.

Advantages include:

Separation of concerns: Models stay pure; query logic lives in the builder.
Chaining and fluency: Organize complex queries with beautiful method chains.
Testability: Isolated query logic makes for easier unit tests.

Example: Custom Product query builder

namespace App\Models\Builders;
use Illuminate\Database\Eloquent\Builder;
class ProductBuilder extends Builder {
    public function active() {
        return $this->where('active', true);
    }
    public function inStock() {
        return $this->where('stock', '>', 0);
    }
}

// In Product model
class Product extends Model {
    public function newEloquentBuilder($query) {
        return new ProductBuilder($query);
    }
}

// Usage
$products = Product::active()->inStock()->get();

Models stay clean — your query methods live together, ready to be chained anywhere.

Core Differences (“Trait vs Builder” for Laravel Devs)

Trait:

Great for generic, reusable logic and simple query scopes.
Can contain non-query methods (helpers, relationships, events).
Easy to apply across models.
Can muddy the waters if abused (model bloating, cross-dependencies).

Custom Builder:

Centralizes query logic, especially as complexity grows.
Keeps models slim and efficient.
Fluent, chainable, and expressive.

Continue reading on Medium »

Enums: How Laravel Devs Cut bugs by 50%

Manjeet Singh — Thu, 09 Oct 2025 13:31:58 +0000

You are building your Laravel app with Inertia.js, everything works perfectly until you try to update a record with a file upload. Text fields update fine, but files mysteriously vanish into thin air. Sound familiar?

This is one of the most frustrating bugs Laravel developers face when working with Inertia.js. The good news is that you are not alone and there are proven solutions. Let me walk you through the 5 most common issues with PUT and PATCH file uploads and exactly how to tackle each one.

The Root Cause Behind the Mystery

Before diving into solutions, you need to understand why this happens. PHP and many server-side frameworks do not natively process multipart/form-data requests for PUT, PATCH, or DELETE methods. This limitation exists at the PHP core level, not in Laravel or Inertia itself.

When you send a file using PUT or PATCH, PHP simply cannot parse the incoming FormData object the same way it does for POST requests. The data arrives at your server but remains unparsed in the raw input stream.

Issue 1: Files Not Received in Laravel Controller

This is the classic problem. You submit your form with a file using form.patch() and when you dump the request in your controller, the file is null or missing entirely.

Here is what typically fails:

const form = useForm({
  name: 'Product Name',
  image: null
})

function update() {
  form.patch(route('products.update', product.id))
}

In your Laravel controller, request file image returns null even though you selected a file.

The Solution:

Use method spoofing by switching to POST and adding the underscore method field. Laravel recognizes this pattern and treats your request as PUT or PATCH.

import { router } from '@inertiajs/vue3'

const form = useForm({
  _method: 'put',
  name: 'Product Name', 
  image: null
})

function update() {
  form.post(route('products.update', product.id))
}

Alternatively, use the router directly:

router.post(`/products/${product.id}`, {
  _method: 'put',
  name: form.name,
  image: form.image
})

This workaround leverages Laravel’s built-in method spoofing support, which checks for the underscore method field and routes your request correctly.

Issue 2: Empty Request Data with `FormData`

Sometimes the entire request arrives empty when you use PUT or PATCH with files. Your request all returns an empty array and even text fields go missing.

Continue reading on Medium »

PHP 8.4 + Laravel: Building Bulletproof Apps with Type Safety

Manjeet Singh — Tue, 07 Oct 2025 13:02:04 +0000

In 2025, with PHP 8.4 hitting its stride and Laravel 12 leaning hard into type hints, we’re finally ditching those “undefined index” nigh...

Continue reading on Medium »

7 Laravel Mistakes Even Seasoned Devs Make — Fix Them Before They Bite You

Manjeet Singh — Tue, 30 Sep 2025 13:02:07 +0000

Hey fellow Laravel artisans, I’m Manjeet, and I’ve been knee-deep in Laravel projects for years now. Whether you’re just starting out or…

Continue reading on Medium »

Stop Guessing Batch Status: Laravel 12 Job Batching With Real-Time Progress

Manjeet Singh — Thu, 18 Sep 2025 13:02:06 +0000

Bulk notifications that time out, clog workers, and leave dashboards guessing aren’t a scaling strategy — they’re a fire drill. The real…

Continue reading on Medium »

5 Non‑Negotiable Laravel Security Practices Developers Must Follow

Manjeet Singh — Tue, 16 Sep 2025 13:01:57 +0000

After years building and auditing Laravel apps, these five non‑negotiable security habits have kept incidents rare and confidence high.

Continue reading on Medium »

DEV Community: Manjeet Singh

Laravel AI SDK Guide 2026

My 8 Years in Dev: The Mindset and Practices That Make You a Better Developer

Trait or Builder? The Complete Guide Every Laravel Developer Should Read

Why This Topic Matters

What is a Trait in Laravel?

What is a Custom Eloquent Builder?

Core Differences (“Trait vs Builder” for Laravel Devs)

Trait:

Custom Builder:

Enums: How Laravel Devs Cut bugs by 50%

The Root Cause Behind the Mystery

Issue 1: Files Not Received in Laravel Controller

Here is what typically fails:

The Solution:

Issue 2: Empty Request Data with FormData

PHP 8.4 + Laravel: Building Bulletproof Apps with Type Safety

7 Laravel Mistakes Even Seasoned Devs Make — Fix Them Before They Bite You

Stop Guessing Batch Status: Laravel 12 Job Batching With Real-Time Progress

5 Non‑Negotiable Laravel Security Practices Developers Must Follow

Issue 2: Empty Request Data with `FormData`