Previously slash commands would fetch the prefix and prepend this to the fake message content. This is stupid. I instead just made bot.get_prefix check if it is a _FakeSlashMessage then return "/" so the prefix is always / when using a slash command.
Checklist
If code changes were made then they have been tested.
I have updated the documentation to reflect the changes.
This PR fixes an issue.
This PR adds something new (e.g. new method or parameters).
This PR is a breaking change (e.g. methods or parameters removed/renamed)
This PR is not a code change (e.g. documentation, README, ...)
<!-- Pull requests that do not fill this information in will likely be closed -->
## Summary
<!-- What is this pull request for? Does it fix any issues? -->
Previously slash commands would fetch the prefix and prepend this to the fake message content. This is stupid. I instead just made `bot.get_prefix` check if it is a `_FakeSlashMessage` then return `"/"` so the prefix is always `/` when using a slash command.
## Checklist
<!-- Put an x inside [ ] to check it, like so: [x] -->
- [x] If code changes were made then they have been tested.
- [ ] I have updated the documentation to reflect the changes.
- [ ] This PR fixes an issue.
- [ ] This PR adds something new (e.g. new method or parameters).
- [ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
- [ ] This PR is **not** a code change (e.g. documentation, README, ...)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Previously slash commands would fetch the prefix and prepend this to the fake message content. This is stupid. I instead just made
bot.get_prefixcheck if it is a_FakeSlashMessagethen return"/"so the prefix is always/when using a slash command.Checklist