Skip to content
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

Open
silasary opened this issue Aug 20, 2023 · 7 comments
Open

[META] 6.0 Breaking Changes wishlist #1537

silasary opened this issue Aug 20, 2023 · 7 comments
Labels
breaking This contains breaking changes enhancement New feature or request help wanted Extra attention is needed on hold This issue/PR is on hold pending higher priority issues/PRs

Comments

@silasary
Copy link
Member

silasary commented Aug 20, 2023

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.

  • Change voice state cache to index as (guild_id, id) (See discussion in Fix bot voice state connection issues #1533)
  • Rename GuildText and co to be GuildTextChannel
  • Make Prefixed and Hybrid commands core library features. (The tech debt of hacking in hybrid commands justifies this)
@AstreaTSS
Copy link
Member

I'd like to add making Snowflake.__int__ actually return an int to the list, as it seems like some users are getting warnings that making __int__ return subclasses of int may be removed in future versions.

@AstreaTSS
Copy link
Member

AstreaTSS commented Aug 25, 2023

More things:

  • [BUG] Images doesn't return all the image in the embed. #1508 and [BUG] modal_callback #1517.
  • For autocomplete, make ctx.kwargs/args arguments resolve to the correct type (currently, a channel in ctx.kwargs/args will just return the string snowflake ID of said channel).
  • Reduce (and maybe eliminate) fetch_guild from processors and replace it with get_guild and proper None handling, as fetch is often overkill (and might cache things a person doesn't want to cache).

@LordOfPolls
Copy link
Contributor

I go away for 2 weeks... and you make a breaking version /j

Change voice state cache to index as (guild_id, id) (See discussion in #1533)

Agreed - the entire voice cache needs a rethink - its design is very... naive and its creator should be shamed.... oh wait thats me

Rename GuildText and co to be GuildTextChannel

What's the rationale here?

Make Prefixed and Hybrid commands core library features. (The tech debt of hacking in hybrid commands justifies this)

That is very contentious as im sure you know. Has this been voted on?

I'd like to add making Snowflake.int actually return an int to the list, as it seems like some users are getting warnings that making int return subclasses of int may be removed in future versions.

Can you show me these warnings? I don't believe i've come across them

#1508

Agreed

For autocomplete, make ctx.kwargs/args arguments resolve to the correct type (currently, a channel in ctx.kwargs/args will just return the string snowflake ID of said channel).

Agreed

Reduce (and maybe eliminate) fetch_guild from processors and replace it with get_guild and proper None handling, as fetch is often overkill (and might cache things a person doesn't want to cache).

Agreed... under the proviso we need to determine where fetch is actually required, and document this

cc @silasary @AstreaTSS

@AstreaTSS
Copy link
Member

RE the Snowflake issue:

Screenshot_20230826-085107.png

At the very least, even if I can't make it appear myself, I agree with the fact that __int__ should return int.

@i0bs
Copy link
Contributor

i0bs commented Aug 26, 2023

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?

@AstreaTSS
Copy link
Member

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.

@mAxYoLo01
Copy link
Contributor

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)

@eightween eightween pinned this issue Dec 9, 2023
@eightween eightween added enhancement New feature or request help wanted Extra attention is needed breaking This contains breaking changes on hold This issue/PR is on hold pending higher priority issues/PRs labels Dec 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking This contains breaking changes enhancement New feature or request help wanted Extra attention is needed on hold This issue/PR is on hold pending higher priority issues/PRs
Projects
None yet
Development

No branches or pull requests

6 participants