[PR #4121] [MERGED] HSB-450 feature: user last active on #4675

New issue

Closed

opened 2026-03-17 02:11:18 +03:00 by kerem · 0 comments

kerem commented

2026-03-17 02:11:18 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hoppscotch/hoppscotch/pull/4121
Author: @mirarifhasan
Created: 6/13/2024
Status: ✅ Merged
Merged: 6/21/2024
Merged by: @balub

Base: next ← Head: feat/user-last-active-on

📝 Commits (4)

7278309 feat: userLastActiveOnInterceptor added and update func added in userService
28aef4d chore: changed user model parameter description
289c42a chore: commented out docker volume for hopp-old-service
f4345be chore: changed backend to work with secure cookies

📊 Changes

8 files changed (+100 additions, -5 deletions)

View changed files

📝 docker-compose.yml (+2 -2)
➕ packages/hoppscotch-backend/prisma/migrations/20240621062554_user_last_active_on/migration.sql (+2 -0)
📝 packages/hoppscotch-backend/prisma/schema.prisma (+2 -1)
📝 packages/hoppscotch-backend/src/app.module.ts (+5 -1)
➕ packages/hoppscotch-backend/src/interceptors/user-last-active-on.interceptor.ts (+67 -0)
📝 packages/hoppscotch-backend/src/interceptors/user-last-login.interceptor.ts (+0 -1)
📝 packages/hoppscotch-backend/src/user/user.model.ts (+6 -0)
📝 packages/hoppscotch-backend/src/user/user.service.ts (+16 -0)

📄 Description

Closes HSB-450

Description

This PR introduces lastActiveOn column in user table of database to track user's last activity timestamp.

For the client-side note, lastActiveOn field added in GQL model.

Checks

My pull request adheres to the code style of this project
My code requires changes to the documentation
I have updated the documentation as required
All the tests have passed

Additional Information

Nil

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hoppscotch/hoppscotch/pull/4121 **Author:** [@mirarifhasan](https://github.com/mirarifhasan) **Created:** 6/13/2024 **Status:** ✅ Merged **Merged:** 6/21/2024 **Merged by:** [@balub](https://github.com/balub) **Base:** `next` ← **Head:** `feat/user-last-active-on` --- ### 📝 Commits (4) - [`7278309`](https://github.com/hoppscotch/hoppscotch/commit/72783095a5b0ae4dff62c2d6e0079f7ae318e3d2) feat: userLastActiveOnInterceptor added and update func added in userService - [`28aef4d`](https://github.com/hoppscotch/hoppscotch/commit/28aef4d9ed1d4e47bba81fb4f791579a1e1b72fe) chore: changed user model parameter description - [`289c42a`](https://github.com/hoppscotch/hoppscotch/commit/289c42a8e25630776e84db06e3e64d85248f9f80) chore: commented out docker volume for hopp-old-service - [`f4345be`](https://github.com/hoppscotch/hoppscotch/commit/f4345bedc9307519c43718696a28f178b043959a) chore: changed backend to work with secure cookies ### 📊 Changes **8 files changed** (+100 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `docker-compose.yml` (+2 -2) ➕ `packages/hoppscotch-backend/prisma/migrations/20240621062554_user_last_active_on/migration.sql` (+2 -0) 📝 `packages/hoppscotch-backend/prisma/schema.prisma` (+2 -1) 📝 `packages/hoppscotch-backend/src/app.module.ts` (+5 -1) ➕ `packages/hoppscotch-backend/src/interceptors/user-last-active-on.interceptor.ts` (+67 -0) 📝 `packages/hoppscotch-backend/src/interceptors/user-last-login.interceptor.ts` (+0 -1) 📝 `packages/hoppscotch-backend/src/user/user.model.ts` (+6 -0) 📝 `packages/hoppscotch-backend/src/user/user.service.ts` (+16 -0) </details> ### 📄 Description    Closes HSB-450 ### Description  This PR introduces `lastActiveOn` column in `user` table of database to track user's last activity timestamp. For the client-side note, `lastActiveOn` field added in GQL model.  ### Checks  - [x] My pull request adheres to the code style of this project - [ ] My code requires changes to the documentation - [ ] I have updated the documentation as required - [x] All the tests have passed ### Additional Information  Nil --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>