Addressing review comments

Author: lonnieezell

docs/events.md

@@ -9,6 +9,8 @@ Shield fires off several events during the lifecycle of the application that you
       - [login](#login)
       - [failedLogin](#failedlogin)
       - [logout](#logout)
+      - [magicLogin](#magiclogin)
+    - [Event Timing](#event-timing)
 
 ## Responding to Events
 
@@ -66,6 +68,18 @@ When the magic link login fails, the following array will be provided:
 
 Fired immediately after a successful logout. The only argument is the `User` entity.
 
+#### magicLogin
+
+Fired when a user has been successfully logged in via a magic link. This event does not have any parameters passed in. The authenticated user can be discovered through the `auth()` helper.
+
+```php
+Events::on('magicLogin', function() {
+    $user = auth()->user();
+
+    //
+})
+```
+
 ### Event Timing
 
 To learn more about Event timing, please see the list below.

docs/session_auth_event_and_logging.md

@@ -38,5 +38,5 @@ The following is a list of Events and Logging for Session Authenticator.
         - OK → no event
         - NG → no event
     2. Send request with token
-        - OK → event `login` / table `auth_logins`
+        - OK → event `login` and `magicLogin` / table `auth_logins`
         - NG → event `failedLogin` / table `auth_logins`

src/Controllers/MagicLinkController.php

@@ -165,9 +165,9 @@ public function verify(): RedirectResponse
 
         // Give the developer a way to know the user
         // logged in via a magic link.
-        session()->setTempdata('magic_login', true);
+        session()->setTempdata('magicLogin', true);
 
-        Events::trigger('magic_login');
+        Events::trigger('magicLogin');
 
         // Get our login redirect url
         return redirect()->to(config('Auth')->loginRedirect());