Emoji parsing, tidyups
Pre-release
Pre-release
Breaking changes
- DM Channel events do not have the
channel
property anymore. This differs from the previous build where this would always be None due to the deprecation of DMChannelCreate events occurring on v8. - The former also means that a standard Channel event no longer has the
channel
property, only achannel_id
, as there is no guarantee we can have a given channel cached. Guild-related subclasses will still have this attribute. USE_VAD
permission has been renamed toUSE_VOICE_ACTIVITY
role_ids
now includes the ID of the@everyone
role.User.default_avatar
is now calledUser.default_avatar_url
to matchUser.avatar_url
.UnicodeEmoji.from_*
methods are now namedUnicodeEmoji.parse_*
.UnicodeEmoji.from_emoji
is now namedUnicodeEmoji.parse
without the_emoji
suffix.CustomEmoji
no longer has anapp
attribute, as it is now user-creatable. This attribute is still defined onKnownCustomEmoji
however, as this is API generated only.
New Features
- New JSON error codes are available to reference.
- Member
role_ids
now contain the@everyone
role (role with the same ID as the guild). Emoji
now has aparse
method which will parse theCustomEmoji
orUnicodeEmoji
from the given string.UnicodeEmoji.parse
implemented.CustomEmoji.parse
implemented to parse snowflakes or valid emoji mentions.
Other changes
- Voice event documentation is now 50% less sarcastic than before about the broken voice endpoint attribute, as it has now been fixed to use the correct port.
- ...as a result, the port is now no longer hard-coded in Hikari.