Skip to content

Conversation

sahsisunny
Copy link
Contributor

@sahsisunny sahsisunny commented Aug 16, 2023

Date: 18/08/2023
Developer Name: @Pratiyushkumar @ravikumar1002 @manish591 @kotesh-arya

PR Number(s):-

Issue Ticket Number:-

Backend changes
Yes

Frontend Changes
No

Database changes
Yes

Breaking changes (If your feature is breaking/missing something please mention pending tickets)
No

Deployment notes
Any special instructions for the deployment

Tested in staging
Yes

Also attach their screenshots.

OnBoarding issue - When I run users/search/?state=ONBOARDING I get 3 users in staging who have an ONBOARDING state but when I run users/search/?state=ONBOARDING&time=31d I get No Users found the message so since for onBoarding state users we don't have discord joining date that's why it's giving No Users Found

onboarding
time31d

Github created at key #1345 - After creating a new account github_created_at key added in user db

image

Screenshots for PR 1311 ( Archive users if not in discord)

Before: users with roles in_discord and archived false.

Screenshot (85)

API call response:

Screenshot (86)

After: Users with in_discord false's archived role set to true

Screenshot (87)

Feature :
QR scanner

Backend change: Yes
Frontend Change: Yes
API Change : Yes
Video of the working Feature
Screencast from 08-13-2023 12:37:14 AM.webm

Screenshots for 1378 - Update Discord servernames with rds usersname:

Before:

user-nickname-before

Successful API Response:
API-nicknameupdate-success

After:
nickname-update-success

router.patch("/", authenticate, authorizeRoles([SUPERUSER]), users.nonVerifiedDiscordUsers);
router.patch(
"/",
authenticate,

Check failure

Code scanning / CodeQL

Missing rate limiting

This route handler performs [authorization](1), but is not rate-limited. This route handler performs [authorization](2), but is not rate-limited. This route handler performs [authorization](3), but is not rate-limited.
* Add a sample route to test it's working

* FEAT:Add functionality to update discord Nickname

* CHORE: remove console.log's

* TEST: Added for discord-nickname-update controller

* TEST: add message object accessible

* TEST: Added for setUserDiscordNickname

* REFACTOR: added a fixture, removed console.log's
router.post("/tokens", authenticate, authorizeRoles([SUPERUSER]), users.removeTokens);
router.patch(
"/:userId/update-nickname",
authenticate,

Check failure

Code scanning / CodeQL

Missing rate limiting

This route handler performs [authorization](1), but is not rate-limited. This route handler performs [authorization](2), but is not rate-limited. This route handler performs [authorization](3), but is not rate-limited.
router.patch("/", authenticate, eventsValidator.updateEvent, events.updateEvent);
router.patch("/end", authenticate, eventsValidator.endActiveEvent, events.endActiveEvent);
router.post("/:id/peers", authenticate, eventsValidator.addPeerToEvent, events.addPeerToEvent);
router.patch("/:id/peers/kickout", authenticate, eventsValidator.kickoutPeer, events.kickoutPeer);

Check failure

Code scanning / CodeQL

Missing rate limiting

This route handler performs [authorization](1), but is not rate-limited. This route handler performs [authorization](2), but is not rate-limited. This route handler performs [authorization](3), but is not rate-limited.
router.get("/:id", eventsValidator.getEventById, events.getEventById);
router.patch("/", authenticate, eventsValidator.updateEvent, events.updateEvent);
router.patch("/end", authenticate, eventsValidator.endActiveEvent, events.endActiveEvent);
router.post("/:id/peers", authenticate, eventsValidator.addPeerToEvent, events.addPeerToEvent);

Check failure

Code scanning / CodeQL

Missing rate limiting

This route handler performs [authorization](1), but is not rate-limited. This route handler performs [authorization](2), but is not rate-limited. This route handler performs [authorization](3), but is not rate-limited.
* FEATURE: add functionality to fetch task base on filter like assignee and task title

* FIX : fix assignee filter

* FIX : add order by title in status filter

* FIX: task size related issue

* FIX: order all task at initial state

* TEMP

* FIX: change variable name

* FEATURE: add functionality to fetch task based on filter like assignee and task title

* FIX(TEST) : fix failing tests

* REFACTOR:change term to title query param

* TEST: add test for tasks validator chages

* TEST: add test for task utils

* TEST: add test for task models changes

* TEST: add test for task controller(integration test)

* Update test/integration/tasks.test.js

---------

Co-authored-by: Pratiyush Kumar <[email protected]>
Copy link
Contributor

@prakashchoudhary07 prakashchoudhary07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not to be merged

sahsisunny and others added 2 commits August 22, 2023 22:26
* FIX: overdue tasks query issue

* FIX: overdue tasks query issue
* Adding isMember param to show membership of the user

* reverting script

* populating membership details only when flag is set

* Adding tests

* fixing PR comments: more specific checks for flags

* Handling firebase limitation of 30 comparision

* PR comments: semantical fix
@prakashchoudhary07 prakashchoudhary07 self-requested a review August 24, 2023 00:08
@prakashchoudhary07 prakashchoudhary07 merged commit da8412e into main Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.