SQLx encode/decode support #2514

This replaces the `[u64; 2]` shard info with `ShardInfo { id: u32, total: u32 }`. Co-authored-by: nickelc <[email protected]>

…s#1997)

The `enum_number!` macro now takes the whole enum definition and generates `From` trait implementations to convert a value to the enum and back. The implementations can then be picked up by `serde` with `#[serde(from = "u8", into = "u8")]` to (de)serialize the types. ``` enum_number! { #[derive(Clone, Copy, Debug, Deserialize, Serialize)] #[serde(from = "u8", into = "u8")] pub enum Foo { A = 1, B = 2, _ => Unknown(u8), } } ``` BREAKING CHANGE: The `Unknown` variant now takes the unknown value and the removed `fn num() -> u64` method can be replaced with `let v = u8::from(kind)`.

Before `ShardInfo`: `[serenity::gateway::shard]: [Shard [15, 33]] ...` Currently: `[serenity::gateway::shard]: [Shard ShardInfo { id: 15, total: 33 }] ...` After: `[serenity::gateway::shard]: [ShardInfo { id: 15, total: 33 }] ...`

The returned `Result` is already marked as `#[must_use]`.

…renity-rs#2015)

…enity-rs#2011)

…#2023)

Both `Value` types implement `From` for their number variants.

The structs are almost identical except for the `focused` field for the current autocompleted option and that the `resolved` data map is not sent for autocomplete interactions. The entities from the `CommandData::resolved` data map are no longer cloned for the option values during deserialization. But the resolved options and values can be accessed via the `CommandData::options()` method. For autocomplete interactions `CommandData::autocomplete()` returns the current autocompleted option + value. BREAKING CHANGES: - `ApplicationCommandInteraction` is now used for application commands and their autocomplete interaction. - The `CommandDataOptionValue`'s variants no longer have the cloned entities from the `CommandData::resolved` data map. See the `CommandData::options` method. - The fields `value`, `kind`, `options` and `focused` of `CommandDataOption` are streamlined into the `CommandDataOptionValue` enum with new variants for subcommands, subcommand groups and autocomplete.

…Overwrite` (serenity-rs#2042)

Co-authored-by: Michael Krasnitski <[email protected]>

…nity-rs#2047)

To simplify the deserialisation implementation for `Event`, it was changed to use serde's native support for `enum` representations that are adjacently tagged (meaning in a text form like JSON, the tag is in one field, the data in the other field). This helped in trimming the lines of code we have to maintain; however, it did break reaction events whose names are prepended `MESSAGE_`, which serde could not account for when renaming, for instance, `ReactionAdd` to SCREAMING_SNAKE_CASE -> `REACTION_ADD`, when it should have been `MESSAGE_REACTION_ADD`. This commit manually renames the reaction events to have `MESSAGE_` at the beginning of their event names.

…rs#2019)" This reverts commit de05e5b because it broke shard code to the point where it just crashes, preventing from even a simple ping-pong bot from running.

…`u32` (serenity-rs#2054)

…rs#2057)

Additionally, adapt some code to the `next` branch.

…#2061) Co-authored-by: Michael Krasnitski <[email protected]>

Due to how the permissions lookups were being performed, the Futures were being marked `!Send` because `GuildRef` is also `!Send`. So, we unfortunately have to clone the guild we get from the cache.

…erenity-rs#2072)

…ty-rs#2078)

…ed (serenity-rs#2083)

…#2090)

This commit adds enforcement for unconditionally required fields on builders. It does so by removing the implementation of `Default` on those builders and adding a `new` method that takes the required fields as argument.

…serenity-rs#2104) If the `Webhook::token` field is `None` when these functions are called, attempt to use the alternate authenticated endpoint instead of erroring. Also, add audit_log_reason parameter to `Http::edit_webhook_with_token`.

)

…ure (serenity-rs#2144)

It was broken due to tokens not being an officially documented format, and the format having changed silently since being implemented. `validate_token` still exists, but it does less intrusive check.

Previously, you couldn't even build Serenity if you had just `http` or just `gateway` enabled. And, `gateway` used to depend on `http` and `utils` which is non-sensical. Both these things are fixed now.

This also adds a new `testing` crate meant to host small snippets to verify correctness for all new pull requests.

…renity-rs#2182)

Documentation had a hard coded list of features (two duplicated copies of them, actually). The new `interactions_endpoint` was not among them, so that API was completely absent from the docs. This commit adds an internal `_docs` feature that enables all features that should be documented. The doc generation now refers to `_docs` instead of writing out the features

…ete` (serenity-rs#2151)

Removes serde_test dependency and cuts down on needless verbosity by testing only what we really need to test. We need to verify *JSON* de-/serialization is correct; where a lot of serde's extra metadata doesn't apply.

…rs#2197)

…line (serenity-rs#2204)

…y-rs#2209)

…lue` dependency (serenity-rs#2211)

This: - removes dependencies: `cfg-if`, `mime`, `tokio-test` - makes dependencies optional: `fxhash`, `mime_guess` - puts each dependency in `Cargo.toml` on a single line - puts dependency attributes in consistent order (version, package/path, default-features, features, optional) - groups dependencies by category

This helps reduce the stack size of most types.

…s#2173)

…rs#2215)

…e_users}` (serenity-rs#2210) The idea is that even users on resource contrained devices can enable cache feature, but just disable all the individual caching flags. What remains is the cached fixed-size data: `CachedShardData` and more importantly `CurrentUser`.

) It was just a dumb wrapper around `Vec<CreateActionRow>` anyways.

…l` (serenity-rs#2230)

Global find-and-replace: - ApplicationCommand -> Command - AutoModeration -> AutoMod - GuildScheduledEvent -> ScheduledEvent - MessageComponent -> Component

…erenity-rs#2243)

`ModalInteraction` is just as clear as `ModalSubmitInteraction`

`create_interaction_response -> `respond` `create_followup_message` -> `respond_followup` `delete_original_interaction_response` -> `delete_response` `delete_followup_message` -> `delete_followup` `edit_original_interaction_response` -> `edit_response` `edit_followup_message` -> `edit_followup` `get_interaction_response` -> `get_response`

…enity-rs#2233)

serenity-rs#2228 changed `CreateAutocompleteResponse` to be a stand-alone response struct into just the representation of the `data` response struct field. That's because you are supposed to embed it in the `CreateInteractionResponse` enum now. But I forgot that there exists `create_autocomplete_response`, a convenience function for `create_response`, which took `CreateAutocompleteResponse` directly. After serenity-rs#2228, `create_autocomplete_response` still compiled, but now didn't send a proper response to discord but just its `data` field. This commit removes `create_autocomplete_response` as a temporary fix. For now, you should use `create_response` as for any other interaction response.

- Update Discord docs links on event structs - Add the required gateway intents to every event - On `Cache`, add information which events are used for which cache resource (fixes serenity-rs#1601)

) They are officially released now.

…ity-rs#2246)

…y-rs#2261)

This reverts commit c259280. I presumed it was Github being confused with which changes to show when merging the pull request (serenity-rs#2240), but they were real, reverting a few commits on `next` as a result.

Reported in rust-lang/rust-clippy#9798

While developing the automod regex PR, I noticed that HTTP errors include lots of useless info about the URL, but don't even include the HTTP method (POST/GET/PATCH/...). This commit changes that. Old: `Http(UnsuccessfulRequest(ErrorResponse { status_code: 403, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("discord.com")), port: None, path: "/api/v10/guilds/703332075914264606/auto-moderation/rules", query: None, fragment: None }, error: DiscordJsonError { code: 50001, message: "Missing Access", errors: [] } }))` New: `Http(UnsuccessfulRequest(ErrorResponse { status_code: 403, url: "https://discord.com/api/v10/guilds/703332075914264606/auto-moderation/rules", method: POST, error: DiscordJsonError { code: 50001, message: "Missing Access", errors: [] } }))`

…2287)

Some small HTTP refactors, mainly getting rid of cruft and moving some things around: 1. Instead of having a `ratelimiter_disabled` flag, simply wrap `Http::ratelimiter` in `Option`. 2. Use `HttpBuilder` in `Http::new` instead of duplicating construction logic 3. Unify `ban` and `ban_with_reason`, and likewise with the kick methods. The model methods API remains unchanged. 4. Introduce a `SecretString` type to prevent leaking the token, e.g. via `Debug`. 5. Change `Http::proxy` to `Option<String>`, because url parsing is already done before a request is sent out.

This replaces the combination of `RouteInfo` and `Route` with a single `Route` struct, responsible for both the endpoint url and ratelimiting. A `routes!` macro is introduced to easily generate code for each endpoint. And `LightMethod` is inlined for each endpoint into the `Request` struct, as well as any query parameters.

…erenity-rs#2294) `mini-moka` provides a cache implementation `mini_moka::sync::Cache`, which is a successor of `moka::dash::Cache`. Currently Serenity uses `moka::dash::Cache` when `temp_cache` feature is enabled. `mini_moka::sync::Cache` has the same API and functionality as `moka::dash::Cache`, but has fewer external crate dependencies.

…ShardManager::intents()` (serenity-rs#2295)

This renames types related to schedule events back the way they were before commit ea8651, which fixes dispatch as events are serialised/deserialised based on their names.

By: - renaming foo_collector back to await_foo and await_foos - adding IntoFuture impl on collector types - and a deprecated `.build()` method that just redirects to `.stream()`

…SON (serenity-rs#2318)

…erenity::Error` by default (serenity-rs#2326)

…#2327)

…nts` builder (serenity-rs#2335)

This re-adds the negation that was accidentally removed in [e83c277]. [e83c277]: serenity-rs@e83c277#diff-414def8886b02bb26f69e6e93e08fa35e230e7faf2b37cf1614cdf58fe987a5dL429-R426

Update Serenity's dependencies to the latest major versions. This requires a breaking change to the signature of `serenity::json::from_str`. This is to ensure the soundness of calling `simd_json::from_str`, which is unsafe, in that it might modify the underlying string such that it no longer contains valid UTF-8. So, if our wrapper function takes ownership of the buffer, it will be dropped at the end of the function, guaranteeing that invalid UTF-8 cannot be used afterward.

This adds a new builder `CreateForumPost`, and adds relevant methods `{Http, ChannelId, GuildChannel}::create_forum_post`.

…ty-rs#2360) Change the `channel_id` parameter to be required only at execution time. However, since the payload must also include a `channel_id` field, make the field an `Option<ChannelId>` and fill it in at execution time. This also adds support for the `send_start_notification` field. Breaking changes: - Remove `CreateStageInstance::channel_id`. - Remove the `channel_id` parameter of `CreateStageInstance::new`.

This is only relevant for private threads.

…#2367)

…odule (serenity-rs#2371) This also makes `GatewayIntents::auto_moderation_{configuration, execution}` const.

- Add back `Default` impl for `PresenceUser` - Add back removed `Cache` methods - Add back `Channel::category`

Fixes serenity-rs#2322 Probably wouldn't have caused because double slashes are treated by HTTP servers as single slashes in my experience. After a bit of back and forth I opted not to use reqwest methods. Parsing the given proxy in `HttpBuilder` into an `Url` directly means the builder method returns `Result` (or panics) which is both ugly. Also, `Url`'s methods yield the scheme and domain both as `&str`, so we would still just have a string in the internal proxy field instead of a type-safe value. So I kept the current simple solution that gets the job done and just added the fix.

) The bulk of this commit is removing `ShardManagerMonitor`. It was just a background task that received `ShardManagerMessage`'s and called the respective `ShardManager` function. Now, you can just call the respective `ShardManager` function directly.

Except for permission names to avoid an inconsistent deviation from Discord's permission specifiers.

It's a really bad way to extract data from an event and it was only used for `EventCollector`, which has been superseded by the strongly typed generic `collector` function, where you can just extract event data straightforwardly with a match instead of unwrapping related IDs.

…2388) Breaking changes: - `ShardMessenger::new` is not `const` anymore - the required argument wasn't obtainable in a const context anyway - `ShardMessenger::new` takes a `&ShardRunner` instead of a `Sender<ShardRunnerMessage>` now - `ShardRunnerMessage::AddCollector` was removed - to add a collector manually, use `ShardMessenger::add_collector` instead

Breaking changes: - `ShardManager`: - `shard_update` method renamed to `update_shard_latency_and_stage` - `Shard`: - `heartbeat_instants` method removed in favor of the more specific `last_heartbeat_sent` and `last_heartbeat_ack` - `last_heartbeat_sent` and `last_heartbeat_ack` return type changed from `Option<&Instant>` to `Option<Instant>` - `heartbeat_interval` return type changed from `Option<&u64>` to `Option<Duration>` - `check_heartbeat` method renamed to `do_heartbeat`

…ags (serenity-rs#2385)

No breaking changes. Newly added: - `Attachment` fields: `duration_secs`, `waveform` - `MessageFlags` bitflag: `IS_VOICE_MESSAGE` - `model::Error` variant: `CannotEditVoiceMessage` - `Permissions` bitflag: `SEND_VOICE_MESSAGES` discord/discord-api-docs#6082

…nity-rs#2395)

…ty-rs#2397)

* Add Connection::two_way_link * Remove non-existent VoiceServerUpdateEvent::channel_id * Make CurrentUser a type alias to User CurrentUser had a bunch of fields missing, and CurrentUser and User are the same type in Discord docs (it's both just User Object) * Note that MessageApplication is an undocumented subset * Add 3 fields on StageInstance StageInstance::[privacy_level, discoverable_enabled, guild_scheduled_event_id]. Also added StageInstancePrivacyLevel as a new type * Fix copy-paste error in DefaultReaction Discord docs link * Add GuildPreview::stickers * Add Integration::scopes and sort fields * Add Member::flags and new GuildMemberFlags type And sort fields * Add ThreadMember::[member, guild_id] * Add 2 ScheduledEvent fields and a new type Fields: ScheduledEvent::[privacy_level, entity_id] New type: ScheduledEventPrivacyLevel * Add 5 AuditLogs fields and new PartialIntegration type Fields: AuditLogs::[auto_moderation_rules, application_commands, guild_scheduled_events, integrations, threads] * Note for later to rename Rule to AutomodRule * Add ChunkGuildMessage::presences * Add PartialChannel::[thread_metadata, parent_id] * Make FollowedChannel's fields actually public (lol) * Sort Reaction fields * Change GuildUpdateEvent::guild type to Guild * Presence: remove redundant serde-default's and sort fields And unwrap `guild_id` field (`Option<GuildId>` -> `GuildId`) The `#[serde(default)]` were redundant because the fields are required according to Discord docs, and I couldn't find any place in the codebase that relies on them being optional * Remove redundant CurrentUser methods avatar_url, default_avatar_url, face, static_avatar, and tag already have implementations on User (which CurrentUser is now a type alias to) guilds, invite_url, and invite_url_with_oauth2_scopes didn't have much to do with CurrentUser and didn't even access any field of it * Add 2 GuildChannel fields and new type New fields: permissions, default_forum_layout New type: ForumLayoutType * Add MessageReference::fail_if_not_exists * Add 2 Message fields and a new type New fields: position, role_subscription_data New type: RoleSubscriptionData * Add new MessageType's RoleSubscriptionPurchase, InteractionPremiumUpsell, StageStart, StageEnd, StageSpeaker, StageTopic, GuildApplicationPremiumSubscription * Include Discord doc text in ChunkGuildFilter * Remake MessageUpdateEvent By going off Message as the base state, and then commenting out the fields that aren't editable, wrapping the rest in Option, and making the corresponding CacheUpdate implementation * Note in PresenceUser docs that it should base off User * Remosed unused InterimMember * Add Discord docs link for extra Member fields * Add GuildMembersChunkEvent::[not_found, presences] And integrate Discord docs text * Add 5 new InviteCreateEvent fields And integrate Discord docs text New fields: created_at, target_type, target_user, target_application, uses * Add note about Discord schemas to ReactionRemoveEvent * Use Debug derive for VoiceServerUpdateEvent Previously it just reimplemented the derive * Add required permission to GuildAuditLogEntryCreateEvent docs * Sort ReactionRemoveAllEvent fields * Add TypingStartEvent::member and sort fields And integrate Discord doc text * Change UserUpdateEvent::current_user type to User And integrate Discord docs text * Remove non-existent ResumedEvent::trace field * Fix ThreadListSyncEvent::channel_ids field typo * Fix ThreadMembersUpdateEvent::removed_member_ids field typo * Sort GuildScheduledEventUser[Add, Remove]Event fields * Add Activity::created_at And remove redundant #[serde(default)] on the kind/type * Fix PresenceUser Discord docs link * Remove 2 Ready fields, add 2 Removed presences, private_channels, trac Added resume_gateway_url And sorted the fields * Add Invite::scheduled_event * Update InviteGuild * ADDENDUM update InviteGuild * Make InviteStageInstance fields pub * Added 7 new User fields and a new type New fields: system, mfa_enabled, locale, verified, email, flags, premium_type New type: PremiumType And sorted User fields * Remove non-existent VoiceState::token field * Add 4 Webhook fields New fields: application_id, source_guild, source_channel, url And sorted fields * Add Command::nsfw * Add CurrentApplicationInfo::role_connections_verification_url * Add Attachment::description waveform and duration_secs are still missing; they're coming with serenity-rs#2392 * Fix Reaction::member field type * Update TriggerMetadata fields and make them pub * Update Trigger Adds allow_list field to Trigger::Keyword Changes KeywordPreset from tuple variant to struct variant and adds allow_list field Adds Trigger::MentionSpam Removes Trigger::HarmfulLink (doesn't exist anymore in Discord docs, it's presumably deleted) Removes the internal InterimTriggerMetadata in favor of TriggerMetadata (they modeled the same fields, just with negliglible ownership difference). * Fix Integration struct Fixes expire_behavior typo and makes the guild_id optional because it's only sent sometimes * Add more documentation to PartialMember * Add more documentation to ThreadMember * Sort Guild fields and 5 new fields New fields: unavailable, scheduled_events, premium_progress_bar_enabled, max_stage_video_channel_users, icon_hash * Add GuildInfo::features and sort fields * Update PartialGuild by basing off Guild * Add 3 RoleTags fields New fields: subscription_listing_id, available_for_purchase, guild_connections * Add 2 Permissions flags VIEW_CREATOR_MONETIZATION_ANALYTICS and USE_SOUNDBOARD * Update ApplicationFlags flags Incorporated Discord doc text Added APPLICATION_AUTO_MODERATION_RULE_CREATE_BADGE and APPLICATION_COMMAND_BADGE Fixed bitflag integers for VERIFICATION_PENDING_GUILD_LIMIT, EMBEDDED, GATEWAY_MESSAGE_CONTENT, GATEWAY_MESSAGE_CONTENT_LIMITED * Add 2 SystemChannelFlags flags SUPPRESS_ROLE_SUBSCRIPTION_PURCHASE_NOTIFICATIONS and SUPPRESS_ROLE_SUBSCRIPTION_PURCHASE_NOTIFICATION_REPLIES * Note deliberately omitted `summary` field in CurrentApplicationInfo * Sort BotGateway fields * Add channel field to [Command, Component, Modal]Interaction * Remove InviteTargetType::Normal and fix EmmbeddedApplication typo * Add StickerFormatType::Gif * Improve some docs * Add Scope::RoleConnectionsWrite and fix RelactionshipsRead typo * Add ChannelType::GroupDm Bots don't support group DMs but it's still important to support in serenity for OAuth2 discord/discord-api-docs#426 * Fix SortOrder::CreationData wrong enum value * Add AutoModAction::[FlagToChannel, UserCommunicationDisabled] * Add Action::BlockMessage::custom_message * Update Discord status page related schemas * Add some Discord docs link (no field changes required) * Update SelectMenu and SelectMenuOption Added Discord docs links Added SelectMenu::[channel_types, disabled] Removed SelectMenu::values (this was from the time Discord accidentally deployed select menu support in modals. But they yanked it, and it wasn't documented anyways) * Update InputText It was completely out-of-date. CreateInputText duplicated all of its fields, and only CreateInputText was kept up-to-date. I made CreateInputText use InputText internally now, to keep up-to-date and not have duplicated fields Added InputText::{style, label, min_length, max_length, required, placeholder}. Changed InputText::value type from String to Option<String> - that's what it says in the Discord docs, and the field needs to be optional anyways now to be usable within CreateInputText * Fix three wrong field types marked by TODOs * Make MessageUpdateEvent's update code available publically This is useful for e.g. poise, which previously had to reimplement it https://github.com/serenity-rs/poise/blob/77e4d3a4897657c91c743f5b45a5d8975b0a778d/src/track_edits.rs#L7-L48

Fixes serenity-rs#1433

…y-rs#2391)

This was overlooked due to an annoying serde-derive footgun: serde-rs/serde#2249 (comment)

This moves to a new toolchain action, uses a new caching action and fixes the Windows CI failing.

Previous execution path of ShardManager::shutdown: ``` ShardManager::shutdown() sends ShardQueuerMessage::ShutdownShard to ShardQueuer::run() calls ShardQueuer::shutdown() sends ShardRunnerMessage::Shutdown to ShardRunner::recv() calls ShardRunner::handle_rx_value() calls ShardRunner::checked_shutdown() calls ShardManager::shutdown_finished() sends ACK to ShardManager::shutdown(), which can now finally return ``` New execution path: ``` ShardManager::shutdown() calls Shard::shutdown() ``` To do that, ShardManager needed direct access to the Shard instance (instead of only sending messages to ShardRunner). So I added a `shard: Arc<Mutex<Shard>>` field to `ShardRunnerInfo` (`ShardManager` contains a `runners: Arc<Mutex<HashMap<ShardId, ShardRunnerInfo>>>`). This also meant ShardRunner couldn't own the Shard directly anymore but needed to store an `Arc<Mutex<Shard>>` too and lock it when needed. This makes for a bit of an ugly diff in shard_runner.rs but oh well. After this, I removed shutdown related functions from ShardRunner and ShardQueuer (and the corresponding enum variants from ShardRunnerMessage and ShardQueuerMessage). Instead there's now just a single simple `shutdown` function on `Shard`, which is called directly by `ShardManager`.

All other builder types in that module belong to an HTTP request and clearly represent that request's fields as per Discord documentation. `CreateQuickModal` doesn't; it's an arbitrary abstraction on top of multiple HTTP requests (and gateway events, violating the pattern that the builder module doesn't have anything to do with gateway). This kind of feature fits better in the `utils` module. This also opens the possibility to add `serde::Serialize + serde::Deserialize` bounds to the `Builder` trait (cc serenity-rs#2337).

…_components` builder (serenity-rs#2335)" (serenity-rs#2413) This reverts commit 851ddc4. The decision to add `Deserialize` impls for all builders has been pushed back to be made only after the 0.12 release. Considering this commit was a partial implementation (only for `CreateComponents`), keeping it would be inconsistent.

…ames (serenity-rs#2415)

This removes the unintentionally-exposed `User::edit`, which was confusing. The `edit` function can now only be called on `CurrentUser`, which upholds the requirement that a user can only edit their own profile.

…he` (serenity-rs#2422) This is used in poise and it should be useful even when `cache` is disabled.

`FromStrAndCache` is like `ArgumentConvert` but worse (was only implemented for `Channel` and `Role`, supported only cache retrieval and no on-demand async requests, and it had no access to the channel ID and guild ID it was called in). `StrExt` was a simple extension trait with a single `parse_cached()` method that called out to `FromStrAndCache`.

Discord says they are required, implied for both send and receive direction, but they're only required for sending. When receiving, they are apparently missing. discord/discord-api-docs#6141

…n a bit (serenity-rs#2428) A few things: - Rewrite `user_permissions_in` - Change `ModelError::InvalidPermissions` fields from `(Permissions)` to `{ required: Permissions, present: Permissions }` - Deprecate `role_permissions_in`/`permissions_for_role` - Change `has_perms` to `require_perms` and reduce boilerplate - Implement `member_permissions` in terms of `_user_permissions_in` (de-duplicate permission calculation code)

* Add a bunch of CreateChannel fields * Add a bunch of EditChannel fields * Make CreateEmbed{Author, Footer} into newtypes * Add CreateCommand::nsfw and sort fields * CreateInteractionResponseFollowup Sort fields and remove username and avatar_url because those are only supported in webhooks * Make EditInteractionResponse newtype over EditWebhookMessage Replaced EditWebhookMessage's methods with EditInteractionResponse's ones (they function the same) and make EditInteractionResponse delegate * Make AutocompleteChoice alias to CommandOptionChoice They're same according to Discord * Add CreateMessage::nonce * Sort CreateScheduledEvent fields * Add CreateStageInstance::privacy_level * CreateSticker: remove optional fields from constructor * Make CreateGuildWelcomeChannel newtype * Add EditGuild::premium_progress_bar_enabled * Add EditMember::flags * Add EditScheduledEvent::privacy_level * Add EditStageInstance::privacy_level * Add EditThread::{rate_limit_per_user, flags} * Add ExecuteWebhook::thread_name * Fix WebhookIncomming misspelling

Cleans up the model prelude by removing some re-exports, namely: - Don't re-export all the submodules of `model` - Don't re-export 3rd party types that are only used internally - Define the `Color` type alias in `model::colour` - Clean up collisions around `automod::EventType` by not glob-exporting from `guild::automod::*` Note that `guild::audit_log` and `guild::automod` still end up getting re-exported via `guild::*`, but I'm not sure how to address that without manually re-exporting each type from `guild`, which would be annoying.

…renity-rs#2436)

…serenity-rs#2441)

I previously had commented some out in https://github.com/serenity-rs/serenity/pull/2393/files#diff-ae030146ad938ad8598138dec5f70cd4a4d3df75907295fc933f3d281a54430dL423-L448 because they cannot change in message update events. But unbeknownst to me, Discord doesn't send only the changed fields, but it sends some fields even when they didn't change. The safer thing is to have just every single field of `Message`'s fields also in `MessageUpdateEvent`.

…rator` (serenity-rs#2445)

discord/discord-api-docs@625a0c2

…y-rs#2456)

…ity-rs#2457)

…erenity-rs#2460)

This converts the hex representation that is used across the API into a much smaller (56 vs 17) type which improves type safety, saves space, and reduces heap allocations (only during a clone).

…delete_message`, and `Webhook::get_message`. (serenity-rs#2465)

This commit reduces the sizes of many integer fields, or converts data to enums when appropriate: - Reduce the size of rate_limit fields - Reduce the size of channel position - Reduce size of role position - Use an enum for `auto_archive_duration` - `DefaultReaction` -> `ForumEmoji` - Swap `AfkTimeout` for enum - Reduce `Sticker::sort_value` to u16 - Reduce size of `min`/`max_values` - Reduce size of `max_uses` and `max_age` - Reduce size of `ActivityParty::size` - Reduce size of `Ready::version` - Reduce `InputText::min/max_length` - Reduce `size`/`width`/`height` -- Discord filesize limits mean we won't hit the size limit, and therefore won't hit height/width limits, plus discord rejects 0 sized files so we can use `NonZero*` - Reduce size of `mention_total_limit` - Reduce size of `RoleSubscriptionData::total_months_subscribed` -- This gives us ~5000 years of role subscription - Fix Change sizes

This alters attribute parse code in `command_attr` to not parse attributes like `#[rustfmt::skip]` as its own, and instead should emit them in the output of the macros.

…Hash` (serenity-rs#2467) This saves an allocation on creation of `ImageHash`.

…erenity-rs#2477) Fixes serenity-rs#2476

…erenity-rs#2472) Signed-off-by: Miezhiko <[email protected]>

…ebhook::url`) are None (serenity-rs#2484)

This reverts commit f63e1a4.

…erenity-rs#2496) Untangles dependencies on the `model` and `utils` feature from the `http` feature, allowing compilation without them.

This allows custom statuses to be used. See: discord/discord-api-docs#6345

Currently only supports IDs, might expand to guilds/users/etc as a utility in the future, depending on PR feedback.

)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SQLx encode/decode support #2514

SQLx encode/decode support #2514

Commits on May 30, 2023

Commits on Jun 1, 2023

Commits on Jun 3, 2023

Commits on Jun 5, 2023

Commits on Jun 12, 2023

Commits on Jun 13, 2023

Commits on Jun 16, 2023

Commits on Jun 23, 2023

Commits on Jun 24, 2023

Commits on Jun 25, 2023

Commits on Jun 27, 2023

Commits on Jul 6, 2023

Commits on Jul 11, 2023

Commits on Jul 19, 2023

Commits on Jul 21, 2023

Commits on Aug 9, 2023

Commits on Aug 16, 2023