Files
Verde-Web/app/Http/Controllers/Api/V1/Auth/VerifyEmailController.php
admin 58a7d3680a feat(backend): hardening sprint — docs, schedulers, validation, email + pickup
1. API docs via dedoc/scramble at /docs/api (scoped to api/v1).
   Linked from the admin sidebar Settings group.

2. Scheduled commands registered in routes/console.php:
   - reports:aggregate (02:00) — daily/weekly/monthly aggregations
   - qr:expire (02:30) — flips past-due allocated/active codes to expired
   - trucks:prune-locations (03:00) — drops history older than retention
     window (default 7 days, config('verde.location_retention_days'))
   All idempotent + withoutOverlapping. --dry flags on qr:expire and
   trucks:prune-locations for safe inspection.

3. Trip double-booking validation: AdminTripController::store rejects
   new trips when the team or truck already has a non-cancelled trip on
   the same date. override_conflicts: true bypasses for emergencies.
   Cancelled trips don't block rebooking.

4a. Email verification: User implements MustVerifyEmail.
    VerifyEmailNotification overrides verificationUrl() for our
    namespaced route. Register sends the link automatically (best
    effort, won't block signup). POST /auth/email/resend (auth) +
    GET /auth/email/verify/{id}/{hash} (signed URL).

4b. Password change while logged in: POST /me/password validates
    current_password, requires the new password to differ, revokes
    every other active token on success — current session stays.

5a. PickupImminent notification: when TripStop -> arrived,
    TripExecutor::notifyAssignedHouseholds() finds households whose
    assigned_drop_off_point_id matches and sends DB + SMS.

5b. Auto-geofence on truck location: TruckTracker::record() now
    auto-fires TripExecutor::arriveAtDumpsite() when an in-progress
    trip's truck pings inside its dumpsite boundary. The executor's
    status guard prevents duplicate timeline events if the driver also
    presses arrive-dumpsite manually.

190 feature tests passing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-01 17:13:00 +08:00

62 lines
1.7 KiB
PHP

<?php
namespace App\Http\Controllers\Api\V1\Auth;
use App\Http\Controllers\Api\V1\ApiController;
use App\Models\User;
use Illuminate\Http\JsonResponse;
use Illuminate\Http\Request;
class VerifyEmailController extends ApiController
{
/**
* Resident clicks the link in the verification email. Laravel signs
* the URL with the user's id + a hash of their email; we re-validate
* here and flip email_verified_at.
*
* Route is wrapped in `signed` middleware which verifies the URL
* signature before this method runs.
*/
public function verify(Request $request, int $id, string $hash): JsonResponse
{
$user = User::find($id);
if (! $user) {
return $this->fail('Invalid verification link', null, 404);
}
if (! hash_equals(sha1($user->getEmailForVerification()), $hash)) {
return $this->fail('Invalid verification link', null, 403);
}
if ($user->hasVerifiedEmail()) {
return $this->ok(['already_verified' => true], 'Email already verified');
}
$user->markEmailAsVerified();
return $this->ok([
'verified' => true,
'email' => $user->email,
], 'Email verified');
}
/**
* Send (or resend) the verification email to the authenticated user.
*/
public function resend(Request $request): JsonResponse
{
$user = $request->user();
if ($user->hasVerifiedEmail()) {
return $this->ok(['already_verified' => true], 'Email already verified');
}
$user->sendEmailVerificationNotification();
return $this->ok([
'sent' => true,
'destination' => $user->email,
], 'Verification email sent');
}
}