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

Fix breaking change from removing ShardRunnerMessage::Message #274

Merged

Conversation

NateDiamond13
Copy link

Fixed the compiler issue introduced in the "next" branch of serenity with the removal of the Message variant of ShardRunnerMessage enum in e552918.

Copy link
Member

@GnomedDev GnomedDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to merge, can you fix the doc CI failure or should I later?

@NateDiamond13
Copy link
Author

Cool, I'll let you handle the CI doc stuff when you get the chance

@GnomedDev GnomedDev merged commit 8741608 into serenity-rs:serenity-next Mar 21, 2025
8 of 10 checks passed
Comment on lines +178 to +180
channel_id: channel_id
.map(ChannelId::get)
.map(serenity::all::ChannelId::from),

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the roundtrip from ChannelId to u64 and back again?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Songbird defines its own ID newtypes to be independent of whichever gateway a user wants, and the input is in our ID format. We have a From impl from serenity and twilight types to ours, but not apparently the opposite direction (hence the transformation here, I guess).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants