-
-
Notifications
You must be signed in to change notification settings - Fork 455
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
Separate ApplicationContext.respond() and followup() #645
Conversation
In my opinion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple suggestions aimed towards dynamically getting the class name for better maintainability, and I also renamed followup to send_followup, and followup_webhook to followup. I'll look over it and see about what @Dorukyum said about the changes though.
Head branch was pushed to by a user without write access
Co-authored-by: BobDotCom <71356958+BobDotCom@users.noreply.github.com>
Co-authored-by: BobDotCom <71356958+BobDotCom@users.noreply.github.com>
Co-authored-by: BobDotCom <71356958+BobDotCom@users.noreply.github.com>
Co-authored-by: BobDotCom <71356958+BobDotCom@users.noreply.github.com>
plskillme x_x Co-authored-by: BobDotCom <71356958+BobDotCom@users.noreply.github.com>
Co-authored-by: Dorukyum <53639936+Dorukyum@users.noreply.github.com>
Summary
Closes #438
This PR aims to separate
ApplicationContext.respond()
andApplicationContext.followup()
(new function) into two seperate functions. It also renamesApplicationContext.followup
(attribute) toApplicationContext.followup_webhook
, but I am honestly unsure how to resolve this naming conflict, so please let me know if this should be adjusted.Checklist
type: ignore
comments were used, a comment is also left explaining why