RealDevSquad / RealDevSquad/website-backend

Update User Properties on Verification

Open
#1,394 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

bug-fix enhancement
Dominant language
JavaScript
Stars
74
Forks
276
Avg merge
1d 26m
Merged PRs (30d)
14

Description

Issue: Update User Properties on Verification

Description

Currently, when users verify themselves, their account properties are not being appropriately updated in our system. To ensure accurate user management, we need to implement changes that set the "archived" property to false and the "in_discord" property to true for users upon successful verification.

Problem

The current verification process does not update user properties, leading to incorrect information in our user database. This can result in challenges when managing user accounts and interactions.

Proposed Solution

Upon successful verification, we need to:

  1. Set the "archived" property to false for users, indicating that their account is active.
  2. Set the "in_discord" property to true, indicating that the user is verified and present in our Discord community.

Benefits

  1. Accurate User Management: Updating user properties post-verification ensures that our database contains up-to-date and accurate user information.
  2. Enhanced Engagement: Identifying users as "in_discord" allows us to tailor engagement and interactions based on their verified status.
  3. Reduced Confusion: Setting "archived" to false clarifies the user's account status and avoids confusion in account management.

Implementation Steps

  1. Modify the verification process to include property updates upon successful verification.
  2. Update the user's "archived" and "in_discord" properties in the backend system.

Related Components

  • User verification process
  • User database management

Acceptance Criteria

Upon user verification:

  • The user's "archived" property is set to false.
  • The user's "in_discord" property is set to true.
  • The changes are accurately reflected in the backend user database.
  • Write text cases and ensure good coverage

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.