-
-
Notifications
You must be signed in to change notification settings - Fork 317
DiscordAPI Empty message error fixed #1183
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
base: feature/empty_api
Are you sure you want to change the base?
Conversation
📦 🤖 A new release has been made for this pull request.To play around with this PR, pull Images are available for x86_64 and ARM64.
|
Xeravax
left a comment
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.
Please solve the lints if you could/
BlueNecko
left a comment
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.
The lints problem has been fixed.
|
sorry for the late reply, but the mentioned type check faliure was already fixed by commit 60c1c21 |
|
lmao, fun. THanks anyway |


Fixes #1051
Fixed the empty message issue upon empty queue. I dont really know Ts well, and the changes i made were made using aids but i tried to keep the changes to a minimal so that nothing major gets affected. My suggestion would be to add the time set by user at the end of empty queue message.
ThankYou