Add user list page

[oliver3]

Resolves #915

• Rename API endpoint list to user_list
• Add mock data and handler
• Add user list page and its test

Page can be reached from the /dev page.

[github-actions]

Sigrid maintainability feedback

✅ You wrote maintainable code and achieved your objective of 3.5 stars

Show details

Sigrid compared your code against the baseline of 2025-02-06.

👍 What went well?

You fixed or improved 0 refactoring candidates.

👎 What could be better?

You did not introduce any technical debt during your changes, great job!

📚 Remaining technical debt

1 refactoring candidates didn't get better or worse, but are still present in the code you touched.

View this system in Sigrid** to explore your technical debt

⭐️ Sigrid ratings

System property	System on 2025-02-06	Before changes	New/changed code
Volume	5.2	N/A	N/A
Duplication	4.3	5.5	5.5
Unit Size	2.4	4.1	4.1
Unit Complexity	3.4	5.4	5.5
Unit Interfacing	3.0	5.4	5.5
Module Coupling	4.0	5.5	5.5
Component Independence	2.8	N/A	N/A
Component Entanglement	3.7	N/A	N/A
Maintainability	3.6	5.1	5.1

💬 Did you find this feedback helpful?

We would like to know your thoughts to make Sigrid better.
Your username will remain confidential throughout the process.

• ✅ Yes, these findings are useful
• 🔸 The findings are false positives
• 🔹 These findings are not important to me

---

View this system in Sigrid

[jorisleker]

List page looks good to me, with following review remarks:

• Have not been able to test date formatting in the 'last activity' column
• Have not been able to verify all user roles are displayed correctly (only 1 user in database)
• The 'admin' user in the database is an anonymous account, which should be impossible
• The button to add a user is lacking, but will probably be added when the 'add' feature is implemented?

[oliver3]

Thanks @jorisleker ! The frontend preview is also deployed and has more users.

The button will indeed be added later, and fair point about the 'admin', I'll add a fullname to make it more representable in a separate PR.

[codecov]

Codecov Report

Attention: Patch coverage is 99.01961% with 1 line in your changes missing coverage. Please review.

Project coverage is 89.94%. Comparing base (a2ebdfe) to head (2c8ee92).
Report is 5 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
frontend/app/module/users/UserListPage.tsx	97.22%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #965      +/-   ##
==========================================
+ Coverage   89.80%   89.94%   +0.13%     
==========================================
  Files         238      241       +3     
  Lines       12561    12645      +84     
  Branches     1281     1289       +8     
==========================================
+ Hits        11281    11373      +92     
+ Misses       1191     1183       -8     
  Partials       89       89              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jorisleker]

@oliver3 approved changed test, but now thinking: we should probably say 'yesterday 13:37' if last activity was yesterday, and not the day name. Day name for anything 2-6 days ago is fine. Before that, it should be a full date.

Earlier assumption was that Abacus would only be used during a couple of days, but now we have more insights into the NPVV we know that even for GR2026 it will be used during at least 1 week (GSB and CSB seatings are about 1 week apart)

[oliver3]

we should probably say 'yesterday 13:37' if last activity was yesterday, and not the day name. Day name for anything 2-6 days ago is fine. Before that, it should be a full date.

Something like this @jorisleker ?