mirror of
https://github.com/pelican-dev/panel.git
synced 2026-07-16 04:03:50 +03:00
0b0fac7337
The @laravel/passkeys client reads the failure reason from a top-level
"message" field, but Pelican's exception handler renders errors in a
JSON:API envelope ({"errors": [{"detail": ...}]}) without one, so the
client fell back to "Request failed with status 4xx".
Add a middleware scoped to the passkey routes that mirrors the first
error's detail into a "message" field, and catch failures in
authenticateWithPasskey() to show them via a Filament notification
instead of failing silently in the console.