-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unverified role to db and remove on /verify #2257
Add unverified role to db and remove on /verify #2257
Conversation
Left few comments @shobhan-sundar-goutam |
|
Build is failing and it very weird for me. Not done anything that will make the build fail especially in the second commit. Not under feature flag because each parts are either getting triggered from frontend, discord slash command or cron-job. So putting under feature flag would require handling feature flags in the respective places from where the apis are getting called and these are already getting used in production which will result in breaking the entire flow. Also staging and prod test will become a big issue in that case. |
aefead1
to
6bdc786
Compare
fc1afe4
to
d8027cf
Compare
cec8e58
to
6e8b5be
Compare
Date: 19-11-2024
Developer Name: Shobhan Sundar Goutam
Issue Ticket Number
Description
When a new user joins Discord, they are assigned an "Unverified" role/tag. However, this role is currently not stored in the database for tracking. The goal is to update the system so that this "Unverified" role is stored in the database as well. When a user completes the /verify command and authorizes themselves, the "Unverified" role should be removed from both the Discord and the database. Also respective logs are stored during this process.
Documentation Updated?
Under Feature Flag
Database Changes
Breaking Changes
Development Tested?
Screenshots
Screenshot 1
store-delete-unverified-db.mp4
Test Coverage
Screenshot 1