#@discordjs/core
1079 messages · Page 2 of 2 (latest)
be1bbdc feat(core): handle request all guild members ra... - didinele
f618add fix: weird import update - didinele
BREAKING CHANGE: Gateway now requires off once methods
8909010 refactor: error class - didinele
I don't think this override is necessary?
<img width="303" height="74" alt="Image" src="https://github.com/user-attachments/assets/b3a4cd7e-510b-4d41-babb-89ffe9592109" />
<img width="1075" height="585" alt="image" src="https://github.com/user-attachments/assets/23cab794-c429-491f-9af3-d1d46b70f810" />
5fa92a1 refactor: error class again - didinele
* Represents the error thrown when the gateway emits a `RATE_LIMITED` event after a certain request.
One thing I'd like to see is what our request payload is. We do this with DiscordAPIError:
So that would mean adding another parameter that exposes the data we sent, which would be d below ({ ...options, nonce }).
I don't really follow what you think should be added to ws? ws has no mechanism for any of this, other than just sending the request, there's no proper place to throw this error.
as such, exporting it from there makes little sense. at best we can maybe shove it in util?
I mean add this to the package:
We can import that here and in discord.js and throw with it.
Pasting from the above for record-keeping. Relevant #11252 #11253
I get where you're coming from though. we have 3 options:
a. current state of my PRs (generic DiscordjsError is thrown that doesn't contain the full information)
b. we duplicate the class I implemented in core in mainlib
c. we move my error implementation into @discordjs/util and mainlib imports it as well
We've agreed on c.
8469fb3 feat(interactions): support with_response query... - monbrey
610b4bb fix: query is optional for some endpoints (#1... - Jiralite
62f2ca5 feat(monetization): Add get entitlement endpoin... - Jiralite
6f05c96 fix(interactions): wrong return type and missin... - imnaiyar
f040c6f types: Export some core-specific types (#10620) - Jiralite
d4b0f4d fix(interactions): options should be optional... - Jiralite
d4d326b types(interactions): fix overloads (#10702) - imnaiyar
b14d8d9 docs(guild): Remove "all" for listing guild mem... - Jiralite
caa7833 feat(interactions): add launchActivity method (... - imnaiyar
33bfded feat(Client): add request soundboard sounds (#1... - sdanialraza
c60341e feat(GuildsAPI): add getRoleMemberCounts - almeidx
Integrates the new endpoint into the GuildsAPI class.
Upstream:
[discord.js] Branch feat/core-guild-role-member-counts was force-pushed to `9ebc4a1`
943dc19 fix(core): webhook delete query type, removeMem... - almeidx
removeMember()returns 204. Replaced the return with await.- The query on
deleteMessage()should be using a type from discord-api-types, which didn't exist. Depends on:
ec2106f feat(core)!: add query support to getAllMembers - almeidx
[discord.js] Branch feat/core-thread-members-query was force-pushed to `9dbe026`
[discord.js] Branch feat/core-thread-members-query was force-pushed to `5082c5b`
BREAKING CHANGE: getAllMembers has been removed. Use getMembers instead, which accepts an optional query parameter.
Add method for deleting current user application role connection to UsersAPI
Discord API Docs reference:
Discord's documentation moved from https://discord.com/developers/docs to https://docs.discord.com/developers. Going forward we should use the new domain, so this is correct as-is
The anchor is actually not working. And neither do the ones for the other methods above related to application role connection.
Seems like the anchor names changed from the docs migration. Perhaps we should correct them
Regarding https://github.com/discordjs/discord.js/pull/11530#discussion_r3264885613, at the very least, please address the documentation link introduced with this pull request.