return user id and timestamp only

opensaas-sh/blog/src/content/docs/guides/authorization.md

@@ -79,7 +79,7 @@ Authorization on the server-side is the core of your access control logic, and d
 You can authorize access to server-side operations by adding a check for a logged-in user on the `context.user` object which is passed to all operations in Wasp:
 
 ```tsx title="src/server/actions.ts" 
-export const updateCurrentUser: UpdateCurrentUser<...> = async (args, context) => {
+export const someServerAction: SomeServerAction<...> = async (args, context) => {
   if (!context.user) {
     throw new HttpError(401); // throw an error if user is not logged in
   }

template/app/src/user/operations.ts

@@ -31,7 +31,7 @@ export const updateIsUserAdminById: UpdateIsUserAdminById<{ id: string; data: Pi
   return updatedUser;
 };
 
-export const updateCurrentUserLastActiveTimestamp: UpdateCurrentUserLastActiveTimestamp<Pick<User, 'lastActiveTimestamp'>, User> = async ({ lastActiveTimestamp }, context) => {
+export const updateCurrentUserLastActiveTimestamp: UpdateCurrentUserLastActiveTimestamp<void, Pick<User, 'id' | 'lastActiveTimestamp'>> = async (_args, context) => {
   if (!context.user) {
     throw new HttpError(401);
   }
@@ -40,7 +40,13 @@ export const updateCurrentUserLastActiveTimestamp: UpdateCurrentUserLastActiveTi
     where: {
       id: context.user.id,
     },
-    data: {lastActiveTimestamp},
+    data: {
+      lastActiveTimestamp: new Date(),
+    },
+    select: {
+      id: true,
+      lastActiveTimestamp: true,
+    },
   });
 };