-
Notifications
You must be signed in to change notification settings - Fork 184
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
[META] 6.0 Breaking Changes wishlist #1537
Comments
I'd like to add making |
More things:
|
I go away for 2 weeks... and you make a breaking version /j
Agreed - the entire voice cache needs a rethink - its design is very... naive and its creator should be shamed.... oh wait thats me
What's the rationale here?
That is very contentious as im sure you know. Has this been voted on?
Can you show me these warnings? I don't believe i've come across them Agreed
Agreed
Agreed... under the proviso we need to determine where fetch is actually required, and document this |
I'm intrigued by #1508 being here, I believe we agreed this was not a 6.x pressing issue with Discord writing multi attachment data to embeds itself. What's the reason here – because we don't have a property setter function to pretty up the deserialisation process? |
...did we? I don't think we ever said that - the most we said is that we couldn't do it in 5.X because of its nature. Having something to make the deserialization of embeds with those embeds would be nice, IMO. |
The 4 AutoMod events should be renamed to follow the standard set by the library (maybe some other events too, haven't checked all of them) |
While we're not quite at the point of making breaking changes yet, this tracker serves to list things that we want to change when we decide to pull the trigger.
Most of these will be things are important enough to justify a breaking change on their own.
(guild_id, id)
(See discussion in Fix bot voice state connection issues #1533)GuildText
and co to beGuildTextChannel
The text was updated successfully, but these errors were encountered: