AI-Powered Laravel Debugger & Error Handling #Laravel #PHP #AIDebugging

Table of Contents

Day 7: Manual Tagging and Revision History for AI Debugging Logs

In Day 6, we auto-categorized Laravel errors with GPT. Today, we’ll enable manual category overrides via the dashboard and log revision history when a developer updates a category or suggestion.

Step 1: Add Edit Form to Each Log Entry

In resources/views/ai-debugger/index.blade.php, replace the category/suggestion display with an inline edit option:

Update table row:

<td>
    <form method="POST" action="{{ route('ai-debugger.update', $log->id) }}">
        @csrf
        @method('PUT')
        <select name="category" class="form-select form-select-sm">
            @foreach(['Database', 'Authentication', 'Authorization', 'Blade', 'Validation', 'Routing', 'FileSystem', 'Other'] as $cat)
                <option value="{{ $cat }}" {{ $log->category === $cat ? 'selected' : '' }}>
                    {{ $cat }}
                </option>
            @endforeach
        </select>
</td>
<td>
        <textarea name="ai_suggestion" class="form-control form-control-sm">{{ $log->ai_suggestion }}</textarea>
        <button type="submit" class="btn btn-sm btn-success mt-1">Save</button>
    </form>
</td>

Step 2: Define Route and Controller Method

In routes/web.php:

Route::put('/ai-debugger/{log}', [AIDebugLogController::class, 'update'])->name('ai-debugger.update');

In AIDebugLogController.php:

use Illuminate\Support\Facades\Auth;

public function update(Request $request, AIDebugLog $log)
{
    $original = $log->only(['category', 'ai_suggestion']);

    $log->update([
        'category' => $request->input('category'),
        'ai_suggestion' => $request->input('ai_suggestion'),
    ]);

    \Log::info('AI Debug Log updated', [
        'log_id' => $log->id,
        'updated_by' => Auth::user()->email ?? 'system',
        'original' => $original,
        'new' => $log->only(['category', 'ai_suggestion']),
    ]);

    return redirect()->back()->with('success', 'Log updated.');
}

Step 3: Add Flash Message Display (Optional)

In the Blade file:

@if (session('success'))
    <div class="alert alert-success">
        {{ session('success') }}
    </div>
@endif

Step 4: Add Updated_by and History Table (Optional, Advanced)

Create a new migration:

php artisan make:migration create_ai_debug_log_histories_table

public function up()
{
    Schema::create('ai_debug_log_histories', function (Blueprint $table) {
        $table->id();
        $table->foreignId('a_i_debug_log_id')->constrained()->onDelete('cascade');
        $table->string('updated_by')->nullable();
        $table->string('field');
        $table->text('old_value')->nullable();
        $table->text('new_value')->nullable();
        $table->timestamps();
    });
}

Run migration:

php artisan migrate

Then create a LogHistory model and update the controller to save changes (optional for Day 8).

Step 5: Test Manual Overrides

Visit /ai-debugger.
Change a category or suggestion.
Press Save.
Refresh to confirm changes are saved.
Check logs for revision history in storage/logs/laravel.log.

Next Steps

In Day 8, we’ll create a full change history UI for each log, enabling developers to track edits made to AI-generated suggestions and categories over time.

Post Views: 37