-
Notifications
You must be signed in to change notification settings - Fork 18
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
Slashify Interviewer #283
Labels
request
Request for a new feature or other modification
Comments
Oh, didn't realize #277 was up 😅. But, I guess "revamping" isn't at odds with "slashifying" |
If you want to work on this, assign yourself to the issue and connect your branch to the issue :)) I used "revamping" in #277 because I wanted to brainstorm some new features we could add, and slashifying interviews would make that easier. |
I don't have the perms to assign to an issue 😳, could that be done? |
5 tasks
Merged
KuroganeToyama
added a commit
that referenced
this issue
Jan 29, 2024
* Refactored to be just command interface * Added file to manage the command and subcommands * Added file to manage list subcommand * Added file to manage signup subcommand * Added file to manage pause subcommand * Added file to manage profile subcommand * Added file to manage resume subcommand * Added file to manage clear subcommand * Added file to manage domain subcommand * Refactored subcommand structures of interviewer command * Refactored clear subcommand of interviewer * Refactored domain subcommand of interviewer * Refactored list subcommand of interviewer * Refactored pause subcommand of interviewer * Refactored profile subcommand of interviewer * Refactored resume subcommand of interviewer * Refactored signup subcommand of interviewer * Made domain field of domain subcommand required * Fixed bug with list subcommand when database is empty * Fixed linting issues * Modified subcommand comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem and the impact.
Is there an issue you want to solve? Who does this feature impact? How many people will this feature impact? Will this feature be used often? What will happen if we don't implement this feature? Please clearly and concisely describe the problem you are facing.
There are lots of interviewer commands that aren't slashified
Describe your proposed solution(s).
Please provide us with as much detail as possible and feel free to suggest more than one solution if there are alternative solutions. We may follow back up to clarify details we aren't sure of.
Slashify them by replicating what was done for
coin
Deadlines
Do you want it done by a certain date? Describe how urgently you need the feature complete. Please be specific and provide additional context if needed. This will help us with prioritization.
Probably by next week
Additional Information
Feel free to add screenshots or any other contextual information we should know for building this feature.
I'm down to work on this
The text was updated successfully, but these errors were encountered: