Debugging Collection Pipelines with Tinker

When debugging complex collection operations, it’s tempting to scatter dd() or dump() calls throughout your code. But there’s a faster way: break down the pipeline line-by-line in Tinker.

Imagine you have a transformer method that filters and intersects date ranges:

public function transform(DateRange $dateRange, array $validCategories)
{
    $range = $dateRange->toCollection()
        ->filter(fn($date) => $date->isWeekday())
        ->intersect($this->getValidRange($validCategories))
        ->values();
    
    return $range->map(fn($date) => [
        'date' => $date->format('Y-m-d'),
        'available' => true,
    ]);
}

The method works fine in some cases but returns empty arrays in others. Instead of adding debugging statements and re-running the entire request, open Tinker and execute each transformation step:

$dateRange = DateRange::make('2026-03-01', '2026-03-31');
$validCategories = ['standard', 'premium'];

// Step 1: Base collection
$step1 = $dateRange->toCollection();
dump($step1->count()); // 31 dates

// Step 2: After filter
$step2 = $step1->filter(fn($date) => $date->isWeekday());
dump($step2->count()); // 22 weekdays

// Step 3: After intersect
$validRange = $this->getValidRange($validCategories);
$step3 = $step2->intersect($validRange);
dump($step3->count()); // 0 - AHA! The intersect returns nothing

// Now test with different categories
$step3 = $step2->intersect($this->getValidRange(['standard']));
dump($step3->count()); // 10 - works with single category

This reveals the issue: getValidRange() returns incompatible data when multiple categories are passed. The fix: ensure getValidRange() returns a flat collection of dates, not a nested structure.

Why This Approach Works

Breaking down collection pipelines in Tinker is faster than traditional debugging because:

1. No need to rebuild application state — You’re working directly with live data or easily reproducible objects
2. Instant feedback on each transformation — See exactly where the pipeline breaks
3. Easy to test different inputs — Try various categories, date ranges, or edge cases without modifying code
4. Clear visibility — Each step’s output is isolated and inspectable

Bonus: Include Tinker Steps in PR Descriptions

When writing pull request descriptions for complex bug fixes, include the Tinker reproduction steps. Reviewers can reproduce your findings without deploying code, making reviews faster and more focused:

Bug: DateRange filtering returns empty when multiple categories are provided.

Root cause: getValidRange() returns nested arrays instead of flat collection.

Reproduction in Tinker:

$step2->intersect($this->getValidRange(['standard', 'premium']))->count(); // 0
$step2->intersect($this->getValidRange(['standard']))->count(); // 10

This pattern works for any multi-step transformation: API response parsing, query builders with complex scopes, or deeply nested data structures. The key is isolating each step so you can see exactly where expectations diverge from reality.