RealDevSquad / RealDevSquad/website-backend

Removal of backfill script for "in_discord" false role, "in_discord" field in user's data and replacing "in_discord" with NOT "archived" in codebase

Open
#1,966 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue Description

Currently, there is a backfill script in place that adds the "in_discord" role with a value of false to all existing users. With a robust verification process in place, this script is no longer needed. Also, as discord features were built over time "in_discord" and "archived" fields for users have been in flip state i.e when "in_discord" false, archived "true" and vice versa. Hence, the "in_discord" field is now redundant, needs to be replaced with NOT "archived" in all its occurrences in codebase. Further, the "in_discord" field is to be removed from each users' data.

Expected Behavior

Backfill script safely removed, NOT "archived" in use in codebase in place of "in_discord", "in_discord" field removed from users' data.

Current Behavior

Backfill script here is a redundant piece of code and not in use any more. "in_discord" field has become a redundant field with "archived" more in use.

Screenshots

N/A

Reproducibility
  • This issue is reproducible
  • This issue is not reproducible
Steps to Reproduce

N/A

Severity/Priority
  • Critical
  • High
  • Medium
  • Low
Additional Information

This issue is based on and an extension of an old open issue #1404

Checklist
  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.

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.

Research direction

Start by locating the backfill script and searching the codebase for every occurrence of "in_discord", including user data handling and Discord-related paths. Remove the obsolete script and field, replace the checks with NOT "archived", and verify that no "in_discord" references remain and existing user data still behaves correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
api, backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.