Laravel Blade循环问题：按Term分组生成表格并重置$loop->iteration

Hey there! Let's work through this Laravel Blade loop problem you're facing. Your idea of restructuring the data in the controller is totally feasible, and actually, we can make it even cleaner using Laravel's Eloquent relationships to fix both of your current issues.

First, Fix the Controller Logic (The Cleanest Approach) #

Instead of passing separate $terms and $apps collections, we can use Eloquent's withWhereHas to only fetch Terms that have matching Applications (with applicationstate_id = 3), while preloading those sorted Applications in one go. This eliminates empty tables entirely and ensures data is sorted correctly from the database.

Here's how to rewrite your controller code:

$terms = Term::withWhereHas('applications', function ($query) {
    // Filter and sort the Applications for each Term
    $query->where('applicationstate_id', 3)
          ->orderBy('name');
})
->orderBy('id') // Sort Terms by their ID (or use 'caption' if preferred)
->get();

return view('admin.index', compact('terms'));

• withWhereHas ensures we only get Terms that have at least one matching Application (no more empty tables!)
• We preload the sorted Applications directly onto each Term, so no extra queries in the view
• Sorting happens at the database level, which is more efficient than sorting in PHP

Then Update Your Blade View #

Now in your view, you can loop through each Term, and for each, loop through its preloaded Applications. The $loop->iteration will automatically reset to 1 for each Term's inner loop, since each inner @foreach is independent:

@foreach($terms as $term)
    <h2>{{ $term->caption }}</h2>
    <table border="1">
        <thead>
            <tr>
                <th>#</th>
                <th>Application Name</th>
                <!-- Add other columns as needed -->
            </tr>
        </thead>
        <tbody>
            @foreach($term->applications as $app)
                <tr>
                    <td>{{ $loop->iteration }}</td>
                    <td>{{ $app->name }}</td>
                    <!-- Render other Application fields here -->
                </tr>
            @endforeach
        </tbody>
    </table>
@endforeach

• No more empty tables because we only passed Terms with existing Applications
• Each table's row count starts at 1, since $loop->iteration is scoped to the inner @foreach for each Term's Applications

Alternative: Manual Grouping (If You Prefer Your Original Idea) #

Your initial thought of grouping Applications by term_id in the controller is also valid. Here's how to implement that:

Controller code:

// Get sorted Applications grouped by term_id
$groupedApps = Application::where('applicationstate_id', 3)
    ->orderBy('term_id')
    ->orderBy('name')
    ->get()
    ->groupBy('term_id');

// Get only Terms that have grouped Applications
$terms = Term::whereIn('id', $groupedApps->keys())
    ->orderBy('id')
    ->get();

return view('admin.index', compact('terms', 'groupedApps'));

Blade view:

@foreach($terms as $term)
    <h2>{{ $term->caption }}</h2>
    <table border="1">
        <thead>
            <tr>
                <th>#</th>
                <th>Application Name</th>
            </tr>
        </thead>
        <tbody>
            @foreach($groupedApps[$term->id] as $app)
                <tr>
                    <td>{{ $loop->iteration }}</td>
                    <td>{{ $app->name }}</td>
                </tr>
            @endforeach
        </tbody>
    </table>
@endforeach

This works too, but it requires two separate queries instead of the more efficient eager loading approach with withWhereHas.

Why the Eloquent Approach is Better #

• Cleaner code: Leverages Laravel's relationship system instead of manual grouping
• Better performance: Reduces the number of database queries (eager loading is optimized)
• Maintainable: Easier to adjust filters or sorting later without rewriting grouping logic

内容的提问来源于stack exchange，提问作者Tomino5