Closed ceSchueler closed 1 year ago
Dummy command seems like a bad idea in a production environment.. I recommend staff members to read the instructions instead of adding a whole new, resettable command.
1) Won't fix: the moment you have >1 spam this issue is gone forever 2) Won't implement: Dummy command is a dumb idea 3) Renaming: Implemented all but the following:
4) cantfix: This does not seem to be the case, specific id's immediately show the full app 5) Wontfix: This doesn't seem necessary 6) Wontfix: I don't understand the necessity behind this?
/see-apps subcommand:spam
to match all other subcommands in appearance (when empty).see-apps
) instead introduce dummy command with example applications.dummy-
and manipulating test-dataRenaming:
Applicant name
→Applicant Name
first name
→First Name
Second Opinion required
→Second Opinion Required
Time zone
→Time Zone
Hours available per week
→Hours Available per Week
Why staff?
→Why do you want to become a staff member?
Why do you want to become a staff member
→Why do you want to become a staff member?
Contribute reason
→How will you contribute if you become a staff member?
How can you contribute if you are given staff
→How will you contribute if you become a staff member?
Submission time
→Submission Time
Like / Dislikes
→Likes / Dislikes
If introductory embed is not removed generally:
/see-apps specific_id
Consider:
/see-apps
into/see-applications
OR/see-sapps
(see staff apps)list
in command to group optionsall
,spam
accepted
denied
Might have some more when the dummy command is here, since we now only have a real application now and I can't test anymore...