backend/utils/user_utils.py (1)

30-35: Consider using get_full_name() for more user-friendly display names.

The current approach derives the display name from the email prefix (user.email.split("@")[0]). However, the User model extends Django's AbstractUser, which provides first_name and last_name fields and a get_full_name() method specifically for this purpose. Seed data in the repository already populates these fields when creating users.

Using get_full_name() would produce more readable names (e.g., "John Doe" instead of "john.doe.123") when available.

♻️ Proposed refactor to use get_full_name()

     lookup = {}
     for user in User.objects.filter(pk__in=pk_set):
-        display_name = user.email.split("@")[0] if user.email else user.username
+        display_name = (
+            user.get_full_name()
+            or (user.email.split("@")[0] if user.email else None)
+            or user.username
+        )
         info = {"name": display_name, "email": user.email}
         lookup[str(user.pk)] = info

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@backend/utils/user_utils.py` around lines 30 - 35, Replace the current
display name logic inside the loop that builds lookup (the for user in
User.objects.filter(...) block) to prefer Django's user.get_full_name() when
available; specifically, set display_name = user.get_full_name() if that returns
a non-empty string, otherwise fall back to user.email.split("@")[0] if
user.email exists, and finally to user.username — update only the assignment of
display_name so lookup[str(user.pk)] = info remains unchanged.

backend/utils/user_utils.py (1)

32-37: Consider limiting fetched fields for query efficiency.

Since only pk, first_name, last_name, email, and username are used, you could use only() to avoid fetching unused columns.

♻️ Proposed optimization

-    for user in User.objects.filter(pk__in=pk_set):
+    for user in User.objects.filter(pk__in=pk_set).only(
+        "pk", "first_name", "last_name", "email", "username"
+    ):

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@backend/utils/user_utils.py` around lines 32 - 37, Looping over
User.objects.filter(pk__in=pk_set) fetches full rows; restrict columns by adding
.only('pk', 'first_name', 'last_name', 'email', 'username') to the query used in
this loop in backend/utils/user_utils.py so that the display name computation
(user.get_full_name(), user.email, user.username) only loads those fields and
avoids pulling unused columns.