Add user login tracking

[SlimDeluxe]

The user model should include login tracking info.
New columns / model attributes:

• Last login date + time
• Total number of logins

The following features are needed:

• When a user logs in, update the "last login" column and increase the login counter
• Include the columns in the Filament resource (shown by default)
• Make the columns filterable

Feature tests must be included.

[SlimDeluxe]

/bounty $50

[algora-pbc]

## 💎 $50 bounty • DataLinx

### Steps to solve:
1. Start working: Comment /attempt #2 with your implementation plan
2. Submit work: Create a pull request including /claim #2 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to DataLinx/eclipsephp-core!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @sparkybug	Mar 15, 2025, 9:38:19 AM	#3

[sparkybug]

Hello @SlimDeluxe , which env variables are required to run this project locally on windows?

[SlimDeluxe]

Hi @sparkybug , thank your for your interest 👍
The project is in the early stages, I am still setting stuff up and adding issues and bounties.

Have you seen the docs here?
With Windows WSL you can install PHP and composer.
Lando is also available, so you should be able to work with Windows. You can use another setup of course, but I chose Lando and can provide help with it.

[sparkybug]

Hi @sparkybug , thank your for your interest 👍 The project is in the early stages, I am still setting stuff up and adding issues and bounties.

Have you seen the docs here? With Windows WSL you can install PHP and composer. Lando is also available, so you should be able to work with Windows. You can use another setup of course, but I chose Lando and can provide help with it.

I have PHP and Composer already installed. The issue is, the cloned repo doesn't come with an env file.
Also gone through the docs but the getting started section isn't clear enough.

[sparkybug]

Hello @SlimDeluxe

/attempt #2

Implementation Plan for Login Tracking Feature

I have successfully implemented login tracking in the User model by:

---

1️⃣ Database Changes

• Added two new columns to the users table:
  • last_login_at (datetime, nullable) → Stores the last login timestamp.
  • login_count (integer, default 0) → Tracks the total number of logins.
• Ensured these fields are included in the package’s migrations.

---

2️⃣ Updating Login Tracking on User Authentication

• Modified the User.php model to include a method updateLoginTracking(), which:
  • Sets last_login_at to the current timestamp.
  • Increments login_count by 1.
• This method is called when a user logs in, ensuring tracking updates.

---

3️⃣ Displaying Login Data in Filament

• Updated UserResource.php to:
  • Display last_login_at and login_count in the Filament table.
  • Enable sorting and filtering for these columns.
  • Ensure users can toggle the visibility of these fields.

---

4️⃣ Writing Comprehensive Pest PHP Tests

• Created LoginTrackingTest.php to verify:
  • ✅ New users start with last_login_at = null and login_count = 0.
  • ✅ Logging in updates last_login_at and increments login_count.
  • ✅ Multiple logins correctly increment login_count.
  • ✅ Logout does not reset login tracking.
  • ✅ Unauthenticated users cannot access login tracking.

---

5️⃣ Package Compatibility Adjustments

• Ensured migrations are automatically registered inside EclipseServiceProvider.php.
• Added proper default values to prevent NULL issues.

---

✅ Summary

This implementation ensures accurate tracking of user logins without breaking existing functionality. 🚀

Options

• Cancel my attempt

[algora-pbc]

💡 @sparkybug submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[SlimDeluxe]

@sparkybug thank you, I will look into it shortly 🙂