Upgrade Rust SDK to spec 1.5.2

This commit is contained in:
VRCCat
2021-10-31 01:17:08 +00:00
parent 7567269b87
commit f8357416a6
33 changed files with 1132 additions and 36 deletions

View File

@ -54,7 +54,7 @@ pub enum RequestInviteError {
pub enum ResetInviteMessageError {
Status400(crate::models::Error),
Status401(crate::models::Error),
Status404(crate::models::InlineResponse404),
Status404(crate::models::Error),
Status429(crate::models::Error),
UnknownValue(serde_json::Value),
}
@ -191,7 +191,7 @@ pub fn request_invite(configuration: &configuration::Configuration, user_id: &st
}
}
/// Resets a single Invite Message back to it's original message, and then returns a list of all of them. Admin Credentials are required to update messages of other users! Resetting a message respects the rate-limit, so it is not possible to reset within the 60 minutes countdown. Resetting it does however not set the rate-limit to 60 like when editing it. It is possible to edit it right after resetting it. Trying to edit a message before the cooldown timer expires results in a 429 \"Too Fast Error\". Message type refers to a different collection of messages, used during different types of responses. * `message` = Message during a normal invite * `response` = Message when replying to a message * `request` = Message when requesting an invite * `requestResponse` = Message when replying to a request for invite The DELETE endpoint does not have/require any request body.
/// Resets a single Invite Message back to its original message, and then returns a list of all of them. Admin Credentials are required to update messages of other users! Resetting a message respects the rate-limit, so it is not possible to reset within the 60 minutes countdown. Resetting it does however not set the rate-limit to 60 like when editing it. It is possible to edit it right after resetting it. Trying to edit a message before the cooldown timer expires results in a 429 \"Too Fast Error\". Message type refers to a different collection of messages, used during different types of responses. * `message` = Message during a normal invite * `response` = Message when replying to a message * `request` = Message when requesting an invite * `requestResponse` = Message when replying to a request for invite The DELETE endpoint does not have/require any request body.
pub fn reset_invite_message(configuration: &configuration::Configuration, user_id: &str, message_type: &str, slot: i32) -> Result<Vec<crate::models::InviteMessage>, Error<ResetInviteMessageError>> {
let local_var_configuration = configuration;