| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The events were cluttering the `model` module, and so are now moved into
their own `model::event` module.
As users should not usually have to work with events all that much -
only currently in some rarely used event handlers - this change should
not be much more effort to import from.
i.e.:
```rs
use serenity::model::event::ChannelPinsAckEvent;
```
vs. the now-old:
```rs
use serenity::model::ChannelPinsAckEvent;
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The command system assumed that prefixes were only one character long,
so count the total length of the prefix. In addition, the
`allow_whitespace` configuration added some difficulty in deciding where
to count as the initial position to start splitting for arguments.
Instead of fixing that, rewrite the framework to make these types of
changes easier in the future.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The option allows whitespace to be optional between a mention and a
command.
Setting it to true will allow the following scenario to occur, while
false will not:
```
<@BOT_ID>about
// bot process and executes the "about" command if it exists
```
|
| |
|
|
|
| |
Allow frameworks to be made and dispatched to that listen for mentions,
but not for prefixes.
|
| |
|