Skip to content

Conversation

@Brainicism
Copy link
Owner

No description provided.

TTtie and others added 30 commits March 4, 2023 14:55
* chore(package): fine tune the description

* chore(package): set package.json version to 0.1.0 🎉
* chore: set package.json version to 0.2.0-dev

* chore: remove deprecated APIs
…aha#47)

* chore(examples/components): fix typo

* SELECT_MENU -> STRING_SELECT

---------

Co-authored-by: TTtie <[email protected]>
* fix(Channel): replace removed constants

* fix(Message): update removed constants
* feat(Constants.Permissions): add new permissions
Ref: discord/discord-api-docs@1909153

* fix linting issues
* refactor(interactions): clean up properties

Removes segments of code from derived interaction classes that execute the same code as the base Interaction class, effectively making the fields being set twice (once in the Interaction class and then in the derived class

* lint: remove Permission imports
* refactor(interactions): use the new `channel` field

Ref: discord/discord-api-docs@88a7618

* use a better type for PossiblyUncachedInteractionChannel
* Initial guild onboarding support

* link to guild onboarding structure in the JSDoc
* feat: voice message support

Ref: discord/discord-api-docs#6082

* keep the waveform as-is

While currently the docs specify it is a base64 byte array, it might be
more worthwhile to give the API consumer a raw string and let them deal
with it appropriately. Let alone this is probably a more future-proof
variant, as (although very unlikely) the format could change in the future.
* add support for join raid protection

* add safetyAlertsChannelID editGuild() options into the typedefs
* initial unique username system support

* fix up wrong ordering

* add a newline between new member getter

* migrated users have 6 default avatars now

ref: discord/discord-api-docs#6218 (comment)

* emit old globalName in userUpdate

* whoops: global_name -> globalName

* copy note about single "0" discrim to Member.js
* added port option to rest options

* Add docs for the new option

---------

Co-authored-by: TTtie <[email protected]>
* headers option is added to REST options

* fixed linting

* fixed typing

* changed the order of header assignment
* types: RequestHandlerOptions#port should be a number

* correct sorting

p comes before r
* feat: support role flags

Ref: discord/discord-api-docs@1a63582

* lint, correct sorting

* add role flags to guildRoleUpdate
…abahaha#88)

* feat(Client): support `with_counts` parameter in getRESTGuilds()

* update the default fetch limit

* the upper bound is unfortunately also 200 :(
TTtie and others added 30 commits October 28, 2024 00:31
VoiceState takes its ID from the id property on the raw structure, which
isn't assigned on the raw API response. A proper solution for this will
be done in a later release.
…nner object (abalabahaha#182)

Got my notes wrong, it's `oauth2_install_params`, not `install_params`
:(
done because provenance and laziness; a copycat from libsodium, pretty much
…a#185)

This unfortunately broke Message construction entirely, so this is
released as a hotfix
…ha#187)

This was apparently forgotten when I decided to transform the event
object and fell under the radar due to the guilds intent being disabled
on my testing bot.
…balabahaha#188)

Got this error a bunch during deployment... Seems to be because during
the message.channel.guild check it doesn't account for null authors.
…haha#191)

Somehow, this managed to flow under the radar…
Added the types as although they're not useful for most usages (i. e.
sending), they might still be a bit useful when receiving.

Ref:
discord/discord-api-docs@af1843d
…balabahaha#201)

Widening the type makes it better correspond with what can be
passed/returned in JS. However, this may be breaking for consumers that
rely on `AnyChannel` not containing thread types - use
`AnyNonThreadChannel` if this is the case.

Fixes abalabahaha#200.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.