serenity - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Move builtin framework impl to its own module	Zeyla Hellyer	2017-08-19	1	-86/+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	-4/+7
\|
*	Allow the user to be given the original message (as in, the message used to ↵	acdenisSK	2017-08-18	1	-1/+1
\| \| \| \|	construct the `args`)
*	Fix imports	acdenisSK	2017-07-27	1	-3/+3
\|
*	Change the config a bit, and a few nitpicks	acdenisSK	2017-07-27	1	-14/+17
\|
*	rustfmt	acdenisSK	2017-07-27	1	-9/+20
\|
*	Switch from #[doc(hidden)] to pub(crate)	alex	2017-06-14	1	-1/+2
\| \| \| \| \| \|	Switch from using `#[doc(hidden)]` to hide some internal functions to `pub(crate)`. The library now requires rustc 1.18.
*	Move CreateGroup docs to the struct	Zeyla Hellyer	2017-05-28	1	-3/+3
\| \| \| \| \|	The docs were on the impl, when instead they should be on the struct itself.
*	Restructure modules	Zeyla Hellyer	2017-05-22	1	-0/+68
	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.