aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* Make Member::guild_id non-optionalZeyla Hellyer2017-06-133-64/+24
| | | | All codepaths result in Some value, so it doesn't need to be optional.
* Only set shard timeout after a READY is receivedZeyla Hellyer2017-06-131-5/+9
|
* Deserialize embed footersZeyla Hellyer2017-06-101-0/+2
|
* Fix negative nonces failing to deserializeZeyla Hellyer2017-06-103-3/+83
| | | | | | | | | | Negative message nonces caused deserialization errors, as serde would not deserialize integers into strings. To fix this, change `Message::nonce` into an `Option<Snowflake>` from an `Option<String>`. This new `Snowflake` is a wrapper around an `i64`. Use a new `I64Visitor` to deserialize i64s, u64s, and strs into the wanted i64.
* Fix voice compilationZeyla Hellyer2017-06-105-67/+102
|
* Use an https connector in http::send_filesZeyla Hellyer2017-06-091-1/+5
|
* Fix shard doctestsZeyla Hellyer2017-06-071-7/+7
|
* Upgrade rust-websocket, rust-openssl, and hyperZeyla Hellyer2017-06-0711-259/+302
| | | | | | | | | | | | | | | | Upgrade `rust-websocket` to v0.20, maintaining use of its sync client. This indirectly switches from `rust-openssl` v0.7 - which required openssl-1.0 on all platforms - to `native-tls`, which allows for use of schannel on Windows, Secure Transport on OSX, and openssl-1.1 on other platforms. Additionally, since hyper is no longer even a dependency of rust-websocket, we can safely and easily upgrade to `hyper` v0.10 and `multipart` v0.12. This commit is fairly experimental as it has not been tested on a long-running bot.
* Ws read/write timeout after 90sZeyla Hellyer2017-06-061-1/+25
| | | | | | | | | | Make read/writes to the stream timeout after 90 seconds to prevent a potentially infinitely blocked call. If the timeout is reached, perform a reconnect. This fixes issues such as intermittent internet issues causing a message to never be received, and thus infinitely blocking.
* Make client starts return an errorZeyla Hellyer2017-06-062-2/+39
| | | | | | When returning, the Client would return an Ok(()). Instead, return an error, since there is currently no reason the client would return under "okay" circumstances.
* Make client join shards and returnZeyla Hellyer2017-06-061-4/+8
| | | | | | | | | | Instead of running a loop forever, have the client join threads when they end. This is currently a poor way of having the client eventually end, but for now it's a duck-tape solution, as when one shard completely fails to reboot it's an indicator of a larger issue (invalidated authentication, intermittent network issues, etc.)
* Separate websocket client initializationZeyla Hellyer2017-06-061-12/+10
| | | | | The logic for this was duplicated, and can be easily separated into its own function.
* Deprecate Client::login, add Client::newZeyla Hellyer2017-06-0617-87/+102
|
* Add User::direct_message exampleZeyla Hellyer2017-06-061-4/+26
|
* Clippy lintsZeyla Hellyer2017-06-064-22/+26
|
* Make User::direct_message/dm accept a builderZeyla Hellyer2017-06-061-13/+10
| | | | | | Instead of accepting a `&str`, make `User::direct_message` and `User::dm` accept a `CreateMessage` builder for consistency with related functions.
* Use chrono for struct timestamp fieldsZeyla Hellyer2017-06-0619-70/+139
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Chrono is easier to use than timestamped strings, so they should be automatically deserialized and available for the user, instead of having the user deserialize the strings themselves. These fields have been changed to use a type of `DateTime<FixedOffset>`: - `ChannelPinsUpdateEvent.last_pin_timestamp` - `Group.last_pin_timestamp` - `Guild.joined_at` - `GuildChannel.last_pin_timestamp` - `Invite.created_at` - `Member.joined_at` - `Message.edited_timestamp - `Message.timestamp` - `MessageUpdateEvent.edited_timestamp` - `MessageUpdateEvent.timestamp` - `PrivateChannel.last_pin_timestamp` `Member.joined_at` is now also an `Option`. Previously, if a Guild Member Update was received for a member not in the cache, a new Member would be instantiated with a default String value. This is incorrect behaviour, and has now been replaced with being set to `None` in that case. Id methods' `created_at()` method now return a `chrono::NaiveDateTime` instead of a `time::Timespec`, and `User::created_at` has been updated to reflect that. Additionally, drop `time` as a direct dependency and use chrono for internals.
* Add CurrentUser::face(), User::face()Zeyla Hellyer2017-06-041-0/+24
| | | | | These functions return the user's avatar URL, or their default avatar URL as a fallback.
* Alphabetize CurrentUser/User methodsZeyla Hellyer2017-06-041-35/+35
|
* Fix links to ChannelId::send_filesZeyla Hellyer2017-06-044-8/+8
| | | | | | Helper methods such as `GuildChannel::send_files` linked to the documentation for `ChannelId::send_file`, when they should be linking to `ChannelId::send_files`.
* Make http::send_files accept a slice of bytesZeyla Hellyer2017-06-041-4/+13
| | | | | | Sometimes a user might be working with a buffer of bytes in-memory and not writing to the disk, so `http::AttachmentType` should accept an &[u8].
* Make http::AttachmentType only use borrowed valuesZeyla Hellyer2017-06-046-25/+27
| | | | | With the way AttachmentType is meant to be used by `http::send_files`, none of the values need to be moved, they only need to be borrowed.
* Remove a FQN usage in User::refreshZeyla Hellyer2017-06-041-1/+1
| | | | | Instead of fully qualifying the namespace when using `std::mem::replace`, use just `mem::replace`.
* Move user avatar method logic outZeyla Hellyer2017-06-041-26/+34
| | | | | | The logic for the `User` and `CurrentUser` avatar methods (`avatar_url`, `default_avatar_url`, `static_avatar_url`) were duplicated, so move the logic out and have each method simply call the related function.
* Add CurrentUser::default_avatar_urlZeyla Hellyer2017-06-041-0/+7
| | | | | Add `default_avatar_url` to `CurrentUser` to match `User`'s avatar functions.
* Add Message::channel()Zeyla Hellyer2017-06-041-0/+43
| | | | | The method can be used as a shortcut for retrieving a message's channel from the cache.
* Add some model docs, deprecate Role::edit_roleMaiddog2017-06-0312-35/+174
| | | Deprecate `Role::edit_role` and rename it to `Role::edit`.
* Fix compilations across feature combinationsZeyla Hellyer2017-06-0222-61/+94
|
* Add User::refreshZeyla Hellyer2017-06-021-0/+58
|
* Fix client-feature, no-model compilesZeyla Hellyer2017-06-011-3/+21
| | | | | | | Some of the methods used in the client dispatch, namely `Channel::id` and `Message::transform_content`, are not _required_ for functionality by the dispatcher. Since these methods are `model` features, they can be gated behind a `model` feature cfg.
* Fix no-feature compilationsZeyla Hellyer2017-06-011-0/+1
| | | | | | An internal `tag` function created in a previous commit is only required for use when the `"model"` feature is enabled, but the function itself was not gated behind the feature.
* Check last heartbeat acknowledged in heartbeaterZeyla Hellyer2017-06-012-4/+34
| | | | | | | | | | When heartbeating, first ensure that the previous heartbeat was acknowledged. If it wasn't, shutdown the sender and receiver so that an auto-reconnect can take place. When receiving a Heartbeat Acknowledgement, set the `last_heartbeat_acknowledged` to `true` to prevent the auto-reconnect process.
* Deprecate User::getZeyla Hellyer2017-06-011-0/+1
| | | | | | The function no longer fit's a short-lived period of serenity's design, where it would have been preferred to do `User::get(ID)` over `UserId(ID).get()`.
* Deprecate *User::distinct, add *User::tagZeyla Hellyer2017-06-011-16/+73
| | | | | | | | | | `distinct`, although accurate, is an odd name for the method. Deprecate `distinct` on `CurrentUser` and `User` and rename them to `tag`. Additionally, optimize the creation of the resultant String by about 2x. Instead of using the `format!` macro, create a new String with a capacity of 37 and push the username, `'#'`, and write the discriminator in manually.
* Fix ratelimiting::ROUTES doctestZeyla Hellyer2017-05-301-1/+1
| | | | | Values are now wrapped within an Arc<Mutex>, so the example needs to obtain a lock and unwrap it.
* Include more info on ratelimiting debugsZeyla Hellyer2017-05-301-7/+7
| | | | | In addition to the amount of time sleeping, include the route being ratelimited.
* Fix ratelimits causing 429s in certain situationsZeyla Hellyer2017-05-301-17/+18
|
* Add Content for MessageBuilderSkye2017-05-302-11/+195
| | | Allow `push` and `push_safe` to use a flexible syntax for formatting.
* Don't create group in help if no commands to showMaiddog2017-05-301-20/+15
|
* Add documentation and tests for frameworkMaiddog2017-05-303-4/+266
|
* Add cache docsMaiddog2017-05-301-0/+115
|
* Add docs for CurrentUserMaiddog2017-05-301-0/+103
|
* Add _line + _line_safe methods to MessageBuilderMaiddog2017-05-281-0/+250
| | | | | | Add new methods to MessageBuilder to push content similar to the other methods, except with the addition of appending a newline afterwards. This should help prettify some MessageBuilder usage.
* Move CreateGroup docs to the structZeyla Hellyer2017-05-281-3/+3
| | | | | The docs were on the impl, when instead they should be on the struct itself.
* Implement multiple attachmentsKen Swenson2017-05-286-0/+278
|
* impl From<char> for ReactionTypeZeyla Hellyer2017-05-281-0/+27
| | | | This can be used as a helpful shortcut for reactions.
* Add CurrentUser::invite_url methodMaiddog2017-05-271-0/+12
|
* Guild::create_channel doesn't require mutabilityZeyla Hellyer2017-05-271-1/+1
| | | | | Change `Guild::create_channel` to take a non-mutable reference, as mutability isn't required.
* Remove deprecated GuildChannel methodsZeyla Hellyer2017-05-271-51/+0
| | | | | | | | | | | | | Remove the deprecated GuildChannel methods in preparation of an incoming commit modifying GuildChannel. Remove the following deprecated methods: - `get_invites` - `get_message` - `get_messages` - `get_reaction_users` - `get_webhooks`
* Fix incorrect attempted send_file deserializationZeyla Hellyer2017-05-276-0/+38
| | | | | | | | | | | If http::send_file received a non-success status code due to reasons such as sending to an invalid channel Id, not having permissions, or sending too large of a file, then it would still try to deserialize a response as if it were valid. To fix this, ensure that the response is successful. Document that if the file sent is too large, then `HttpError::InvalidRequest(PayloadTooLarge)` is returned.
generated by cgit v1.2.3 (git 2.25.1) at 2026-04-18 19:38:14 +0000