| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Move builtin framework impl to its own module | Zeyla Hellyer | 2017-08-19 | 1 | -348/+0 |
| | | | | | | | | | | | | | | | | | | The framework is now moved in its entirity to the `framework` module, with the `Framework` trait currently on its own and the builtin implementation provided. The builtin implementation has been renamed to "Standard". Upgrade path: Rename the `BuiltinFramework` import to `StandardFramework`. Instead of importing builtin framework items from `serenity::framework`, import them from `serenity::framework::standard`. This is the beginning to #60. The root `framework` module (non-standard implementation) will be built more by the time it's closed. | ||||
| * | Apply rustfmt | Zeyla Hellyer | 2017-08-18 | 1 | -6/+12 |
| | | |||||
| * | Fix failing tests (#133) | Andrej | 2017-07-31 | 1 | -3/+3 |
| | | |||||
| * | Change the config a bit, and a few nitpicks | acdenisSK | 2017-07-27 | 1 | -12/+16 |
| | | |||||
| * | rustfmt | acdenisSK | 2017-07-27 | 1 | -37/+35 |
| | | |||||
| * | Fix #130 | acdenisSK | 2017-07-22 | 1 | -3/+6 |
| | | | | | Removed action support from the builtin one as well, due to it adding some uneccassery complexity and it being only asked upon by one user | ||||
| * | Fix doc tests | acdenisSK | 2017-07-02 | 1 | -4/+8 |
| | | |||||
| * | Remove Context::{channel_id, queue} | Zeyla Hellyer | 2017-06-13 | 1 | -18/+18 |
| | | | | | | | | | | The `channel_id` field on Context is no longer required internally, and is no longer of use to userland as event handlers are given the channel ID in some way where possible. `queue` is a remnant from when the Context was the primary way to interact with the REST API. | ||||
| * | Deprecate Client::login, add Client::new | Zeyla Hellyer | 2017-06-06 | 1 | -3/+8 |
| | | |||||
| * | Clippy lints | Zeyla Hellyer | 2017-06-06 | 1 | -5/+5 |
| | | |||||
| * | Don't create group in help if no commands to show | Maiddog | 2017-05-30 | 1 | -20/+15 |
| | | |||||
| * | Add documentation and tests for framework | Maiddog | 2017-05-30 | 1 | -0/+28 |
| | | |||||
| * | Sort default help by group/command names | Maiddog | 2017-05-24 | 1 | -6/+26 |
| | | | | | | | | Sort the default framework help functions by their group and command names. This should act as a reasonable default for users. If other behaviour is required, users can make their own or copy and modify existing functions. | ||||
| * | Restructure modules | Zeyla Hellyer | 2017-05-22 | 1 | -0/+285 |
| Modules are now separated into a fashion where the library can be used for most use cases, without needing to compile the rest. The core of serenity, with no features enabled, contains only the struct (model) definitions, constants, and prelude. Models do not have most functions compiled in, as that is separated into the `model` feature. The `client` module has been split into 3 modules: `client`, `gateway`, and `http`. `http` contains functions to interact with the REST API. `gateway` contains the Shard to interact with the gateway, requiring `http` for retrieving the gateway URL. `client` requires both of the other features and acts as an abstracted interface over both the gateway and REST APIs, handling the event loop. The `builder` module has been separated from `utils`, and can now be optionally compiled in. It and the `http` feature are required by the `model` feature due to a large number of methods requiring access to them. `utils` now contains a number of utilities, such as the Colour struct, the `MessageBuilder`, and mention parsing functions. Each of the original `ext` modules are still featured, with `cache` not requiring any feature to be enabled, `framework` requiring the `client`, `model`, and `utils`, and `voice` requiring `gateway`. In total the features and their requirements are: - `builder`: none - `cache`: none - `client`: `gateway`, `http` - `framework`: `client`, `model`, `utils` - `gateway`: `http` - `http`: none - `model`: `builder`, `http` - `utils`: none - `voice`: `gateway` The default features are `builder`, `cache`, `client`, `framework`, `gateway`, `model`, `http`, and `utils`. To help with forwards compatibility, modules have been re-exported from their original locations. | |||||