#archive-library-discussion
25217 messages · Page 9 of 26
Yeah exactly but you can add it to that PR
This is probably about CommandInteraction which narrows the type down to the text based channels:
https://github.com/discordjs/discord.js/blob/master/typings/index.d.ts#L506
| PartialDMChannel | null probably needs to be added.
Whats the new activity type competing ?
competing in (whatever)
Nice that, ok bro
I was looking at the CommandInteraction types like space said ^^
btw why is it readonly?
getter
Was there a reason we didnt make ApplicationCommand an extendable structure?
soo does anyone have an opinion on this
Is this in the works? https://github.com/discordjs/discord.js/issues/5855 If I recall correctly it also happens on v13
or is this feature discontinued
#5886 in discordjs/discord.js by monbrey opened 3 days ago (approved)
fix(Message): flags not being parsed on some edits
📥 npm i monbrey/discord.js#fix-message-manager
will the fix come to v12 master?
v12 master?
v12 isnt master
It will come to master
Its up to the maintainers if we continue patching v12 or not
ignore the "master" part of the question xd
lol, Crawl just merged the v13 fix
niceee. is it also a v12 fix?
this is a separate PR
oh 😔
Theres different bugs and different reasons they happen in each version
The suppressEmbeds one is not related to editing out embeds
For discord js -next
Since I know it’s supposed to be vastly different from discord js
What are some ways it could be different? Like how could we create a new instance of client and stuff? I know kyra had some good ideas
afaik -next doesn't even have any shape or form yet
No, it wont be significantly different for the end user as far as Im aware. The intention is to rebuild the internals, not the externals
That’s why I was hoping to spark some sort of discussion where others could pitch in ideas
But its not going to be "vastly different"
getting back to this, is it worth opening a PR to fix this?
@outer raven not sure what that thing has to do in your PR https://github.com/discordjs/discord.js/commit/e0efcc6ab0e3f060e30438c0d990c9465c6134df#diff-86252c6a5caa00d9f8fb12018a8cf70659bc19a5fc2a95f9944c7a2c3e781d96L215-R215
but we all missed it, and it pretty much broke all bots
lol
oh shit
yeah noted, sorry
I thought that was transforming the type into a string, not the other way around
That method is for getting the data to send to the API, so needs to be an int
yeye got it now
On a completely unrelated note though: what do you guys think of merging sub command options into the main interaction's options? Let me explain:
When you run a command with a subcommand or subcommand group, the only option in the main collection will be the sub command that you ran, so if we manage to merge them all into the first there should be no issue (unless an option has the same name as one of the sub commands, which i don't know if it's possible)
merge how?
you still need to know which subcommand was run, are you proposing moving that property up to CommandInteraction#subcommandName or something
no, the subcommands would be kept. What I'm suggesting is adding the options that would otherwise be nested in the subcommand to interaction.options
I dont like the idea of breaking the hierarchy, no
imo it made sense since you'll never have more than 1 option with sub commands and groups but sure then
hmmm actually yeah maybe
I think the part I'd find awkward is that if the subcommand is kept, you'd be getting it essentially like a boolean option I guess? Just checking that its... there, and then you know what the other options are?
When you have multiple subcommands you'd be checking which one the user ran. I usually do this with interaction.options.find(o => o.type === "SUB_COMMAND")
why is code option in #5918 being removed? there's no other clean way to do it without manually writing it into the string
yeah thats why code was very useful for me
but why is adding \ an issue?
not that you would need to read a lot from a bunch of slashes
you can even put that in multiple lines if you prefer
for the codeblock to be formatted properly, you need a single newline after language. no matter if you use ` or ', it has to be there
however, template strings (`) have a bonus of being able to be multiline themselves
We'll have a util available for it
It just wont be a message option anymore
yeah it will just be a function you wrap your string with
will that be included in that PR?
no
We talked about adding that in /builders and then re-exporting in d.js
getting back to this, can I open the PR?
alright
If there's only one possible sub-command at a time, why make people find it as an option when it could be bumped up to a property though
I feel like you could have
interaction#commandName
interaction#subcommand
interaction#subcommandGroup
and then just the options or something
yeah that could work
I'm actually having a hard time figuring out a smart way to merge the two collections since the main interaction.options is only built after the inner options are
so maybe remove it all together would be a good idea and much easier
actually nah even then I have no clue how to do this in a smart way since I'm not familiar with the way djs patches stuff, could you try to do this?
https://github.com/discordjs/discord.js/issues/5855 this issue is closed. Is it fixed for v12? If so, do I just update discordjs or are there extra steps?
AFAIK, there are no additional releases for v12, so you'd have to install from dev. npm i discord.js@dev
The suppressEmbeds bug is different to the empty embeds bug
sort of
It probably shouldnt be closed though
Yeah we have no more releases for v12 planned.
@vernal atlas what are your plans on https://github.com/discordjs/discord.js/pull/5132?
Are you gonna do the largest rebase ever before continuing a lot further? Or split the changes in smaller PRs?
well i was at first going to rebase and continue, but now im thinking that splitting the changes is a good idea
Yeah, smaller ones are also easier to review and merge
@slate nacelle why the confused emoji? https://github.com/discordjs/discord.js/pull/5923#issuecomment-868373891
I wouldn't call the bot property being invalid expected behaivor.
Or at least hope it's not.
Well yeah but the user object I got from fetching an audit log had every property it should and thus it wasn’t classified as a partial so I don’t know any other way to get this information, unless we check for all properties inside the object to determine if its a partial or not
Patching with partial data should not invalidate the state of the object.
If you are not sure a change has to be made, make none.
alright I did a few more tests and I found a solution that worked for me, let me know if there are any other issues
I think I'm missing exactly what you think is incorrect here. You kinda lost me right from the start when you told me you were re-assigning properties to things they aren't meant to be. The identifier on a custom emoji will be its name:id format, while on a unicode emoji, it will be the unicode. It's not ever meant to be the id, which yes, will be null on unicode emojis.
The ReactionEmoji class is kinda like a partial guild emoji, eg when the reaction came from a guild the bot isn't in so it can't get full data I think
yes, but it wont have an id if its unicode
If you need to store them in a database for whatever reason, const unique = emoji.id ?? emoji.identifier
Because it is the identifer at the time
Youre just misusing the property
Its not supposed to be a primary key for a database
#5929 in discordjs/discord.js by SkyFlags opened 1 hour ago (review required)
fix(Message): Make author of referenced message nullable
📥 npm i SkyFlags/discord.js#master
Is there a reason for skipLibCheck being set to true in the tsconfig.json?
Would it make more sense to set that to false to catch errors in the typings?
I have never tried but... I suppose we could add a stub augment
Something likets module '@discordjs/voice' { interface TheInterfaceWeRequireFromIt {} }
If the module is installed, then it'd merge an empty interface with the full one
That way we can use that interface from a module that's otherwise missing, without getting compiler errors
That must be inside declare module 'discord.js' {}, btw
cc: @tacit crypt @fringe temple
Why do we even have @types/ws and discord-api-types as dependencies now, but not @discordjs/voice?
Typings are currently broken on master because there are interfaces imported, that don't exist in the used discord-api-types version.
And with skipLibCheck: true that could easily be missed.
What interfaces exactly?
typings/index.d.ts(142,5): error TS2305: Module '"discord-api-types/v8"' has no exported member 'APIActionRowComponent'.
typings/index.d.ts(147,5): error TS2305: Module '"discord-api-types/v8"' has no exported member 'APIMessageComponent'.
typings/index.d.ts(1634,12): error TS2416: Property 'options' in type 'ReactionCollector' is not assignable to the same property in base type 'Collector<string | `${bigint}`, MessageReaction>'.
Type 'ReactionCollectorOptions' is not assignable to type 'CollectorOptions<[MessageReaction]>'.
Types of property 'filter' are incompatible.
Type 'CollectorFilter<[MessageReaction, User]> | undefined' is not assignable to type 'CollectorFilter<[MessageReaction]> | undefined'.
Type 'CollectorFilter<[MessageReaction, User]>' is not assignable to type 'CollectorFilter<[MessageReaction]>'.
typings/index.d.ts(1640,12): error TS2416: Property 'collect' in type 'ReactionCollector' is not assignable to the same property in base type 'Collector<string | `${bigint}`, MessageReaction>'.
Type '(reaction: MessageReaction) => Promise<string | `${bigint}`>' is not assignable to type '(...args: any[]) => string | `${bigint}`'.
Type 'Promise<string | `${bigint}`>' is not assignable to type 'string | `${bigint}`'.
Type 'Promise<string | `${bigint}`>' is not assignable to type '`${bigint}`'.
Oh that's intentional I think, it's going to be released with the next version
They exist on discord-api-types main so probably.
But I personally think that they shouldn't be ignored in the CI, like they are now, so they don't get missed.
Please add better documentation for FriendlyError and CommandFormatError in Commando 😦
I really want to use something that lets me customize the command format error but there is no clear documentation
Like add use cases and examples
Commando is currently unmaintained
why are snowflakes not just bigints?
Because that's how the api sends them
you can't serialize bigints
that's unfortunate
How does Discord.js achieve seamless ESM-CommonJS interop?
It's not 100% seamless either, as explained in https://github.com/discordjs/discord.js/issues/4670
thanks for this. I think I'll be fine if all issues are that obscure. have you ever considered just dropping CommonJS support?
pretty much everyone uses commonjs though?
but why? I guess that's my real question. why have we not fully embraced ESM?
we meaning the node.js ecosystem
Because requiring cjs inside of mjs is problematic
Or rather the other way around
So our lib couldnt be used outside of mjs anymore
Which is rather problematic
We would have to supply cjs builds
And lets just assume we have a big typescript userbase, the standard tsconfig.json tsc generates does not set the compilation target to ESNext by default either
So we would get daily questions about that 100%
Thats not to mention all glitch/replit users
is it problematic for reasons other than that?
node esm doesn't support json
No, but I would argue this is a big problem indeed
other than users not knowing how to switch, I mean
which is why I've tried esm multiple times and have had to go back to cjs
Yeah, some things are still experimental
hmm can't you read the json the normal way
JSON modules are stage 3 but node doesnt have them yet
theres a lot more cons here: https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
Its a lot of work honestly that is not very clear
tempted to copy this readme
I don't understand this. you can read json files. you just can't abuse import to do it. the normal way is not significantly more work
I still really dont see any reason to just drop support for something that is still in such widespread use
thanks for your answers, my questions were not rhetorical
since discord deprecated Message.stickers and is switching to Message.sticker_items (presumably to not break .stickers), should d.js keep using Message#stickers (with the .sticker_items data) or use Message#stickerItems or similar? (sticker_items contains partial sticker objects)
(personally I like Message#stickers and think Message#stickerItems sounds dumb)
Agreed, we can still make breaking changes to Message#stickers so go for it
also unfortunately the Sticker#fetch discussion is still happening
re https://github.com/discordjs/discord.js/pull/5867#discussion_r658874457
if there's gonna be Sticker#fetchUser to get the user if it's a guild emoji, then what should Sticker#fetch do (since it'll be needed for the partial sticker objects)
vlad says that if it knows that the sticker is in a guild, it should try to fetch with the guild route (which will only work if the bot is in the guild) to try to get sticker.user
I say that it should just run Client#fetchSticker, and people can use Sticker#fetchUser (or GuildStickerManager when that's added) if they want the user
Is it possible for the bot to have/receive a sticker without being in the guild
yes
in messages
or by fetching with the non-guild route (which works for all existing stickers)
itll probably not be in the sticker's guild most of the time
and I think Sticker#fetch should work in that situation
what message would it receive if its not in the guild? or are they like emojis and can be used globally?
latter, if the user has nitro
right
u can already use them if u have android alpha
yeah while it might be nice to be able to have it know where to fetch from I think that would introduce inconsistency in the expected behaviour
Since people will need to call fetchUser anyway?
well if the bot is in the guild and it did the check, you could just do (await sticker.fetch()).user and it would work
but the sticker.fetch() would error if the bot isnt in the server
but it should fallback to the other fetch right?
vlad seemed to want it to let it just throw the DiscordAPIError
but ig we could fallback
Is there a difference between using the @readonly tag or making a type Readonly<> in the docs?
I think only with the tag @readonly this can be showed
Readonly is a typescript type, not something jsdocs would understand
Readonly<T> means that all the properties in T are read-only, but the object can still be 'overwritten' to put it simply
Should this be changed from Record<string, string> to
interface RequestData {
// ..
headers?: {
[K in keyof RequestHeaders]?: RequestHeaders[K];
}
}
I thought for type safety/intellisense. What additional headers are used other than these three?
Makes sense, thanks
the thing is some types in the jsdoc comments have Readonly<> instead of @readonly, should I open a PR to fix this?
As sugden pointed out, @readonly means that the property on the class can't be overwritten, Readonly<T> means that the returned object itself is frozen
So they're not the same
and how can we tell those two apart in the code?
Tell apart where exactly?
Which ones should have @readonly, Readonly<T> or both
Readonly<T> when you use Object.freeze() or a similar method
@readonly usually when you have a getter without a setter
Alright. I just found this odd because Readonly seems to be the only thing the docs don't link
is it worth linking this to ts docs maybe?
😦
Why don’t I get the proper intellisense for ColorResolvable
type ColorResolvable =
| 'DEFAULT'
| 'WHITE'
| 'AQUA'
| 'GREEN'
| 'BLUE'
| 'YELLOW'
| 'PURPLE'
| 'LUMINOUS_VIVID_PINK'
| 'FUCHSIA'
| 'GOLD'
| 'ORANGE'
| 'RED'
| 'GREY'
| 'DARKER_GREY'
| 'NAVY'
| 'DARK_AQUA'
| 'DARK_GREEN'
| 'DARK_BLUE'
| 'DARK_PURPLE'
| 'DARK_VIVID_PINK'
| 'DARK_GOLD'
| 'DARK_ORANGE'
| 'DARK_RED'
| 'DARK_GREY'
| 'LIGHT_GREY'
| 'DARK_NAVY'
| 'BLURPLE'
| 'GREYPLE'
| 'DARK_BUT_NOT_BLACK'
| 'NOT_QUITE_BLACK'
| 'RANDOM'
| [number, number, number]
| number
| string;
``` it doesn’t show these color names with intellisense, maybe it’s just a problem on my end
had a similar issue before, I think it's bc of the | string. Not sure tho
It is
Yeah that’s what I was thinking too
Fixing that rn
#5950 in discordjs/discord.js by kyranet opened 19 seconds ago (review required)
types(ColorResolvable): change string to #${string}
📥 npm i kyranet/discord.js#typings/strict-type-string-color
@sharp wigeon @fallow crater ^
thank you
np 
perhaps something similar to https://github.com/discordjs/discord.js/pull/5144/files#diff-9c03fb4d8c1b03db876641d3900a9c08f5a3a30be8d8a3b9840018507243c284R1477 would be an idea
Why can’t we just link it like a promise or an object?
i guess so
although im not sure because most people don't use typescript (mostly beginners) so it might confuse them
and readonly is pretty self-explanatory by itself
so ill let that be for now
but for future reference this would be the link https://www.typescriptlang.org/docs/handbook/utility-types.html#readonlytype
there should be a way to view the old design of the website
I find it easier to navigate
Won’t be a thing
for threads
Error [GUILD_CHANNEL_RESOLVE]: Could not resolve channel to a guild channel.
at GuildMember.permissionsIn
i sent this to ckohen over a month ago, looks like its still unfixed in master?
Assuming this happens when you pass a ThreadChannel?
Yeah this needs a bit more info
totally forgot you sent me this, I'll fix it in a thread fixup PR that I'm making now
Why was it decided to create the thread channel types with _ instead of the camel casing that is used basically all across the library?
Talking about public_thread, private_thread and news_thread which could be publicThread, privateThread and newsThread
the only places I see _ being used are in full caps names that usually come from Discord's docs
cc: @ruby terrace ^
Also it would be relatively easy to switch to a date-based version number for dev releases. Can I open a PR to change this so that dependabot starts working again and people stop getting confused when they install an old version with npm up? @wild flax
this is my proposal (YYYYmmddHHMM)
No
The hash is handy because it prevents duplicated releases (aka releasing the same commit twice)
And it also helps identifying the commit in GitHub as well
Github tells you on which commit the action ran though
It's extra steps, and also refer to the first point
Ye I know but that doesn’t happen very often since a PR is usually merged every x hours
And even if it does it’ll be once and doesn’t hurt that much
It’s just that I’ve seen way too many people in #djs-help-v14 saying they have the latest version when they don’t because they used npm up
That could also be fixed by deprecating outdated dev versions automatically
Which they are
Are they?
I still do but it should only have 1 not deprecated
At the moment yes
Well yeah but that doesn’t seem to fix the npm up issue unfortunately
Nor dependabot
It did work for me in a test environment Nvm, installing an outdated version and then running npm update won't update to the latest commit
ah ok cuz I was testing and it wasn't working for me
is it really that big of an issue if a "duplicated" version is released? Imo the pros outweigh the cons here
Its also easier for the user to know when the version they have is from
Which they can get from the commit
They have to go on GitHub and find the commit
No, just paste the hash
Way more complicated than looking at a number and getting the day from it
e.g. https://github.com/discordjs/discord.js/commit/5ad83a6a65e5944ceb3a41fee2df40ba1f5b03e4
Yeah it’s still more complicated than looking at a date
Looking at a date is unreliable because GH shows local time while GHA uses another when releasing
There can be several commits on the same date so it won't be unique too
Only 2 unless it’s manually ran
And the date is the least relevant, the day is enough and accurate enough as well
We do multiple releases a day sometimes, tho
The CI runs twice and Crawl sometimes runs it manually. I’ve never seen more than 3 releases in a day
make it 7 SHA and a unix timestamp and I accept it
But that doesn't offer de-duplication, Crawl
13.0.0-dev.7_SHA.UNIX
Fine by me
thats fine, don't care enough, as long as this whining stops
And not like the UNIX timestamp is readable at all
I could find the date a commit's from faster than getting the full date from the timestamp
Wait yeah why not a date
I prefer keeping the system as-is, maybe reduce sha to 7, but that's all
But you can have both
Or none
My proposal was YYYYmmddHHDD but you can add dots in between
yeah but if you do 20200628 you might as well do a unix timestamp
its not for the user anyway
Why not?
its to fix npm
I really don't want to discuss this, its a temporary thing anyway until we have proper pre-releases
Will there be dev releases after v13?
I'm not going to heavily invest into a system thats gone in less than 6 months
Possibly for v14
It’s not a hard fix tbh, just trying to make it more readable I guess
Fine then, I’ll try to find a way to get the unix timestamp and PR
So this is good right
sure
aight, will open rn
so should I change it
aight
what does --verify do?
alright, will commit then
wouldn't it be a good idea to create some guild webhook manager in master, just like how <Guild>.fetchBans() and BanInfo were removed and replaced with a GuildBanManager in v13?
maybe same for invites, integrations, templates, etc?
A new dev version has been released with the changes.
hmm npm up doesn't seem to be picking up on it but it doesn't downgrade either, lemme try dependabot
alright can confirm dependabot is working again, thank you!
@ruby terrace The example doesn't seem to match with what is documented above it here: https://github.com/discordjs/discord.js/blob/3174507d57d9f6011e97b4f3209f42179e050f9b/src/managers/ThreadManager.js#L89
The example says it will create a public thread but it is missing the startMessage param, which according to the docs above means that the thread will be private
I have no choice in this matter, the channel types are lower cased at creation of the channel and constants are UPPER_CASED
Forgot to remove the extra tidbit yeah
only docs for startMessage need to be changed
But this isn't determined by Discord. In fact, channel types in Discord are UPPER_CASED so I think we could change that just to be more consistent across the whole library
there are not many places that I'm aware of where lower_casing is used
We're fighting two different library conventions, parameters are typically camelCased, whereas Constants are UPPER_CASED. I think the lowercaseing of channel types may have been an interesting (unsuccessful) attempt at ensuring camelCase for the properties. Not opposed to changing it, its just a very large whole library refactor
Wait, where are we using lower_case instead of camelCase?
channel types
more specifically news_thread, public_thread and private_thread
channel types get .toLowerCased so I used that for all _thread types everywhere
Yeah I don't blame you and I know it's a large change but so was changing to camelCasing in v10 or whatever it was so, for the sake of consistency, I think we should go for it
just so you know, I'm going to do something about this, don't know what yet though, should have a PR within a day though
Moving here from #archive-interactions since it's probably more relevant, it looks like the typings for followUp on CommandInteraction was removed in https://github.com/discordjs/discord.js/pull/5831, I can't tell if this is intentional or not but I would assume it wasn't?
Looks like it got removed accidentally in the last rebase
Seems like the changes in that PR weren't applied to that function too, unless that function wouldn't need them, I could potentially PR a fix though it may be easier for someone who already has an environment set up
I just fucked up a rebase there and deleted an extra line. Add the type back
That function doesnt need the changes
Alright, will do
can't you simplify that https://github.com/discordjs/discord.js/pull/5976/files#diff-d6774c7fcd0485bec7c183ecf1749f65eea85a05999935ddf4aa7b331ddb4826
with ```js
exports = { ...exports, ...require('@discordjs/builders') };
Not really, because we're exporting ButtonBuilder, EmbedBuilder, MessageBuilder, and a few more, in later PRs to /builders
Which we'd like to expose separately (and outside Formatters, as they're different things)
An alternative, though, is to namespace them in /builders
But that might be bothersome if you use it directly
I was testing thread creation to decide how to document the params and believe me I had to bring out my notebook to write down all the possible ways in which startMessage and type param can be combined. I would share it but it looks horrible. This mess can lead to a lot of potential issues in the support. The solution I want to propose is to have two seperate methods for thread creation just like there are two seperate endpoints for them. For eg: ThreadManager#create and ThreadManager#createFromMessage or something along that line. This will remove all the issues that arise due to possible combinations of startMessage and type param.
It could work, I highly anticipate people to never start a thread from a message using that function, instead using Message#startThread(). That paremeter exists so that can work.
all the possible ways in which
startMessageandtypeparam can be combined.
What do you mean by this though? They can't?
Yes correct, they don't as passing one specific param will do nothing in a particular case as it acts like a noop because something else will get passed no matter what you pass as value for that param. Which is where the issue is. The behaviour is weird because that params will matter sometimes and won't sometimes. We are mixing two endpoints into a single method and hence why this behaviour. I know I'm not making much sense here so I'll make a table to clear what I'm trying to say.
https://i.imgur.com/J4mfNr5.png
As you can see in the table the type param only matters when startMessage isn't provided. This means that type affects nothing in the other three cases. As you pointed out Message#startThread doesn't even talk about type because it takes the type from the message there and that's why it is much more clean. I was thinking about doing the same for manager. A method that creates threads from message and another that creates using type (just like the endpoints). This will seperate these two params into two different methods where their presence/absence does affect the result.
The news _ + type column is wrong, its always news thread
right, my bad
you see the problem here? type really only matters if provided on a text channels thread manager, and technically news_thread is an invalid parameter.
If you create a new function, createWithMessaage for example (cause I think it would be the less used one, called internally mostly) then you still have much of the same issue with create, always creates news in a news channel, but can have errors etc in text
Technically speaking doing this could make it much more type safe for ts users though since news doesn't extend text in that case. You just can't separate it in the actual code
With that, I say do it, adding something like
export class ThreadManager<AllowedThreadType> ... {
public create(options: { ... type?: AllowedThreadType };
}
export class NewsChannel {
public threads: ThreadManager<'news_thread' | 10>;
}
export class TextChannel {
public threads: ThreadManager<'public_thread' | 'private_thread' | 11 | 12>;
}
to make it very type safe
it'll be hard to do for docs, but for ts users? worth it
So, just to be clear you want to:
Restrict values for type depending on type of channel the ThreadManager is on ✅
Want to divide the thread creation on manager into two methods 
Is that correct?
I’m against 2 methods too
It kinda of goes against libraries design
We tried so hard going in a direction where we have a nice single method style
Throwing that overboard seems like a bad thing here
All right then restricting the values for type is what we are going to do
By all means, give a shot to making the docs more clear too, I definitely understand it being confusing but I couldn't think of a better way to document it, the warnings being my best attempt.

I don't remember who exactly but I recall a dev who said that setStatus Status whatever action you want must have their "status" boolean required
So here setLocked needs at least the boolean
Which means JSDoc is probably wrong instead
Discussion happened around MessageButton#setDisabled iirc
@oak quail in fact, both do not work:
Also we don't do it anywhere else in the typings lol
TS is complaining about something
So I expect it to be this, but even then, we don't use it anywhere else, so we shouldnt here
Its introducing inconsistency
hmm it worked until the latest commit which didn't even edit typings
Ah, this explains
yes
#5980 in discordjs/discord.js by DTrombett opened 54 seconds ago (review required)
types(ThreadChannel): make locked and archived param optional
📥 npm i DTrombett/discord.js#locked-patch
@sharp wigeon ^^
beat me to the pr 😂
@remote wasp is 5971 done
yeah, I'll make the changes to docs in the typings PR
🤔 shouldn't it error for me too then? are you on an older version or something
our CI is on 4.3
i'm on typescript@next
Same
I'm waiting on #5979 to fix an issue with my bot, will it be on this night's dev release?
#5979 in discordjs/discord.js by ckohen opened 9 hours ago (approved)
types(ApplicationCommandPermissionsManager): fix types
📥 npm i ckohen/discord.js#permissions-manager-types
Are you going to add type tests? @ruby terrace
want a separate PR for that or in that one?
idm
We usually include tests in the same PR that adds the code
Because how software is usually tested
okie
Will https://www.npmjs.com/package/@discordjs/collection ever be published as just "collection"? I feel like this can be used in many places other than Discord.js and it's overall a good QOL package
Nothing is stopping you from using it outside of discordjs 
Yeah I know but the name makes it seem like it's not intended to be used outside of it. You can still do it but a better name and README would probably reach a broader audience
I don't think anybody cares how wide an audience it reaches, and installing things from a particular organisation is very common
@material-ui/core, @typescript-eslint/parser are a couple of examples that come to mind
Besides
Name is already taken
hm yeah and it seems to be similar
Yeah nvm then, didn't think the name could be taken lol
Wouldn't it be good to have a function for hyperlinks in the builders module?
and to take it one step further, it could return a not worth it and perhaps impossibleHyperlinkString type acceptable only in embed description and field values
... how?
Also, webhooks (and interactions) can send masked urls
#3 in discordjs/builders by vladfrangu opened 15 hours ago (changes requested)
feat(SlashCommands): add slash command builders
📥 npm i discordjs/builders#feat/slash-commands
For example ^
I could add them
Do you want to make the PR? Or do you not mind?
It's the same 👍
#4 in discordjs/builders by kyranet opened 46 seconds ago (review required)
feat(Formatters): added hyperlink and maskLink
📥 npm i kyranet/builders#feat/added-escaped-link-and-masked-link
Done, @zenith oracle ^
Nice! 👍
@outer raven you’ll have to use ~ not > preferably
And we usually just have “no longer supported” as a message
Also npm deprecate is very prone to failure, so best case you should attach a || true
I tried to find the message but they’re all set to “no” xD, will fix
Also what’s the difference between > and ~?
It just fails most of the time that’s what
Lol
No idea why
Npm isn’t giving helpful errors
is > even valid?
it was in the website I used to test and was in one of the examples
Of course I couldn't actually test the command
btw shouldn't the || true be removed from publish so that you know when it fails?
No
I don’t care if it fails
And CI being red just because a dev publish failed is kinda dumb
fair enough, will commit now
Why is there no getter for the owner of a guild in the guild object?
We replaced it with the more reliable fetchOwner, since intents
#5480 in discordjs/discord.js by advaith1 merged 2 months ago
feat(Guild): replace owner with fetchOwner
ahhh alright
right now ApplicationCommandPermissionsManager#fetch() returns ApplicationCommandPermissions[] with the existing registered command permissions but it throws DiscordAPIError: Unknown application command permissions if no permissions are set, probably because that scenario is not handled. Wouldn't an empty array make more sense?
if discord throws an error shouldn't djs throw an error
fair enough
@oak quail whats with the 2 comments from sugden, are they even still relevant
honestly idk
Oh nvm I see
He wants you to make a typedef
And link it to the discord docs
But they arent merged yet
yeah
Also can you confirm a thing for me, I saw MANAGE_EMOJI_AND_STICKERS somewhere thrown around
well just a link I think?
aight
isn't emoji the plural of emote though?
I can see if I can get the docs pr merged today or tomorrow
I wanna add the gw event tho, and test the endpoints
we can't merge stickers without the docs pr anyway, so no rush
also should I add guild sticker manager and the event to this pr? or a new one later
GSM shouldn't be breaking
but I think the intent is getting renamed bc of the new event, so that is breaking
Id say keep it in this PR
and just let us know when you added the stuff
so we know what to look at

About Typings, I think string types can be more specific. For example Channel#toString() returns string for types but it actually returns <#${bigint}>, I think it would be great to have these specific types, especially for TS users...
Maybe we should have multiple Snowflake types so ?
Why?
One for users, one for channels, one for roles etc
Oh I'm dumb these are not IDs, but maybe UserString, ChannelString etc ?
Yep
Maybe <#${Snowflake}> no ?
not bad too
bur missing a $ lol
also a thing about activities
This is the activity of my bot logged in the console but there are some difference between this and what docs and typings show. First of all createdTimestamp is NaN and createdAt invalid date, then id is undefined while it should be a Snowflake and also presence is not documented as a property at all.
Debugging the data received only this is shown and there are no properties about id, createdAt etc...
Is this because the activity is a bot activity?
and should we handle the missing properties?
Ohh wait is this because of intents?
Enable them and check again
What's that
NPM being shit
It worked for my presence but not for the bot's presence, where the result is still the same
Will guild avatars be on the initial release of v13? I know they're not available to everyone yet but they're on the API so everyone should be able to use them with no problems
yeah it isn't merged
I made it a draft because the api docs arent merged either so I assumed it would need to wait for that
but then again selects were merged without even a PR on the dapi docs so idrk
Well however it's a semver minor so I don't think they'll wait for that if v13 is ready
yeah but the PR is ready so it could just be merged even if its not out for everyone the same way it was done with selects and threads i guess
Same as user banners
well but banners arent on the api yet
if they change I think it'll only be on the user's side. The avatar is just a hash similarly to the user avatar
and they have been changing the user interface for guild avatars but that's it
It’s just not how we do things
And I don’t want this to be a reference case
Selects and Threads were different because we are in direct contact with those respective devs
And we wouldn’t release v13 without them either
Ah so you don't know when guild avatars will come?
No
alright that makes more sense
This MessageActionRowOptions interface is causing a false positive that happens when sending an array with one button/select in a message's components. Is it safe to remove or is this covering some edge case?
dont remove it?
unless resolvable covers it
I'd rather you figured out why [button] is assignable to that
yeah I tried but I don't really know since that interface is an object with a components property so it doesn't make much sense
I mean the answer is definitely not removing the type that supports the object format
well then in that case I have no clue how to fix it. It seems like it's completely ignoring the array part in MessageActionRowComponentResolvable
Maybe because it's optional
Can you make components required and see if it still happens?
that does fix it but i wonder if it breaks anything else
but it makes sense that MessageActionRowOptions would require components so I guess that's the fix
MessageActionRowOptions should be like a MessageActionRow without needing to instantiate the class but a MessageActionRow always has a components property, which is an empty array by default.
The problem is that MessageActionRowOptions is the parameter to create a MessageActionRow too, that, as I said, doesn't require to set the components property as it's an empty array by default and that's why that components property is optional
well it's used in the constructor but if you're constructing an action row like that you need to specify some components, otherwise it's a pointless row
You can always add components later with .addComponents
yeah but if you're doing that then you'd just not pass a data object
and that is still fine because data is marked as optional
Making that required means that these are accepted:
new MessageActionRow ();
new MessageActionRow({ components: new MessageButton() });
But not these:
new MessageActionRow({});
message.channel.send({ content, components: [new MessageButton()] })
Which is completely fine in my opinion
Yeah right
Maybe this should be tested a bit more but I think this is the correct solution
yeah those are the only scenarios where this interface is used so i think its fine
great now i cant commit 😐
Oof
got it in another way no worries
#6005 in discordjs/discord.js by ImRodry opened 6 minutes ago (review required)
types(MessageOptions): fix components being optional
📥 npm i ImRodry/discord.js#fix-components-type
there we go
oh
btw @zenith oracle I meant sorting them alphabetically within the region, not within those 4 types
Uhm yeah makes sense...
Should be done. However there are a lot of types without lines and not sorted between the region, but yeah, I think it's better to sort them for consistency
if you want you can probably add those lines, doesn't rly justify a separate PR imo if you're literally just adding empty lines
Why was this removed from README in master?
Probably cause it was either super redundant or super broken
is anyone able to re-run the CI on https://github.com/discordjs/discord.js/pull/6005 ? I think it got stuck
Done
ty
@ruby terrace if a thread is archived when the bot starts, it does not get cached (if it is unarchived) until the bot is restarted
ThreadChannel#sendable is incorrect: it returns true even if it is a private thread that the bot isn't in and the bot doesn't have manage threads
there prob should just be a helper property that returns whether the bot is in the thread
….how do you have that thread in cache then?
I think I did .add on the wrong manager probably, is it in any of the caches? (My hunch is that it’s only in the .threads cache)
Or actually, not, because that’s not how that .add works
I’ll look into it in a bit
not sure but its not in the channel cache
the channel stays cached if the bot was in it earlier
if the bot wasnt in it after starting then interaction.channel is null
Oh, didn’t consider being removed. (Can you tell I ddi most of my testing before permissions were released lol)
I’ll definitely add a getter
tbh i might ask them to just add bots to the thread when a slash command is used
at least for private threads
the bot can just add itself by pinging itself but its annoying to handle
That does kinda make sense, if bot exists in guild add it, don’t know if it’s work for very old bots though (where client is is not the same as application
im sure they can make it work 
they have it working in dms
with /applications/bots/:id or whatever
why does Formatters.time use Math.floor instead of Math.round?
I was considering using Math.trunc tbh
But at the end of the day, it matters nothing because Discord's time syntax isn't precise
Looking at this, this probably happens with normal channels too, but you wouldn't ever encounter it unless you manually removed channels from cache
All fixed here
#6015 in discordjs/discord.js by ckohen opened 19 seconds ago (review required)
fix: correct permissions checks and cache on update
📥 npm i ckohen/discord.js#threads-fixup-2
Can we get a release since there were many breaking changes in the recent commits?
Is Custom Caching planned in Discord-next?
#6013 in discordjs/discord.js by 1Computer1 opened 13 hours ago (changes requested)
feat(Managers): add customizable caching for managers
📥 npm i 1Computer1/discord.js#cachedi
think this is what this PR is trying to achieve
it currently just have cacheManaging for Messages and Presences,is custom prop caching in plan?
im not sure I didn't look much into it, you can see the PR yourself
Not sure what you mean by “custom prop caching”
custom property caching, cache just ids and names, but not colors or....
and discord.js-next, they are doing the rewrite right?
Some properties of the Client class are nullable because instanciated only after the call to the "login" function or there is other reason ?
there could be multiple reasons, depends on what you're talking about
For example "user".
If the Client class has no use without the login function (for the moment I haven't seen any without calling the login function) maybe it would be interesting to make a static function mixing the arguments of the constructor and the arguments of the login function so that some properties are no longer indicated as "nullable" (the user property for)
not sure if that's possible but if you know how to then you can open a PR. The only reason that's nullable is because of the login indeed
I'm not at home, but if this is the only reason, then creating a static method that does both would surely be the best solution.
I'll see if I can make a PR as soon as I get back from vacations
What should this method do?
Like a isLogged()?
And if so what should be return value?
I don't know what to call it but it could be a method named "createInstance(options)". The "options" argument would be the same as the current constructor with the addition of the "token" property which would be mandatory.
Within this function, we would do what the login function does and then we would call the constructor of the class (from now on "private") passing it all the information to create an instance of the Client class which would contain directly the "user" properties (and the other properties depending on the login class).
It is this instance that the static function would return.
To create an instance, users will have to do :
const client = Client.createInstance({ intents: [....], token: "...." })
I don't know if I'm clear or even if it's possible (haven't looked at the code of the client class yet) but if it is, it can be a better method. It would avoid some properties to be nullable
You may want to instantiate a client, but not to login yet (probably to pass your instance reference to your own structures).
This looks more like unsolvable typings issues as this would require TypeScript/your IDE to detect whether Client#login resolved at that particular point of your code, which is likely not possible due to way of code is analyzed and also because that method can fail (invalid token).
You can still "extend" the typings to force certain properties to exist, make a method that would instantiate + login and return that freshly logged in client as that extended type.
You may want to instantiate a client, but not to login yet (probably to pass your instance reference to your own structures).
In this case it is necessary to keep a separate login method but in the opposite case (use of the Client class only after a call to the login method) I don't think it is useful and using a static method will resolved this "unsolvable typings issues". In fact, I have not seen anyone using the Client class without having called the login class 🤷
You can still "extend" the typings to force certain properties to exist, make a method that would instantiate + login and return that freshly logged in client as that extended type.
This is what I do actually. but I thought that if everyone called the login method before doing anything with the client instance the static function was better suited for typing
But the login method is asynchronous, so unless everyone switches to esm to make use of top-level await I think hardly anyone will use that static method
the makeCache option supports changing cache based on manager class name and hold class name
so you can customize all the caches
you cannot customize properties
Hummm if the only way to login is this static method they will use it, no ?
but yeah, thats the problem, you often just need the guild id and not the guild name, guild features, banner url, splashurl.... They are rarely used.
So what do you expect users to do?
Client.createInstance(...).then(client => {
client.on('interactionCreate', ...)
});
```isn't really good user experience
yeah, I played a little bit around with the Library. Disabled all caches and added custom property caching and setted the properties to null, which should be removed.
But the key uses itself memory, so it did not had so a big effect.
The only solution would be do modify the internal Classes, through deleting some keys, when caching them. But I think this will never happen, bc there will be a lot of breaking changes....
10mb on 140k channels, when setting 60% of the properties to null
you have to delete the key itself
Yeah, I don't really see what it changes since, currently, you have to call the login method before you can receive the events.
Actually we do
const client = new Client(.....);
client.on(........)
client.login(token)
With the static we will have
const client = await Client.createInstance(....)
client.on(.......)
I am a minimalistic Person
node does not support top-level-await yet, will it even do at some point lol
so you'd need to wrap this into an self-called async function
Oh right
I just cache Guilds and Roles |channels and emojis, members, precences are not cached
removing the keys changes it to 400mb , setting them to null uses 700mb
Indeed, this can be a problem and the use of "then" can be disturbing
After if you find it disturbing we can stay like that
is this just so you don't have to put a ! after Client#user to assure it's there after login?
Indeed it is to avoid some properties to be marked as nullable 😂
If the majority prefers the current method to the method of the static function we keep the current method.
if you know they're not null at a certain point, just assert 
to keep with the example
Client#user will never be null in any event callback, so you just assert it to not be null and move on with your life
Uh what about making an interface LoggedClient which is just an extension of Client with properties like user not nullable so that we can use a function isX() (like isText() for channels) which returns this is LoggedClient
Many projects I know of use a top level async function, immediate async function, or custom classes/methods to handle awaiting on client login. Passing a logged in client to such custom classes would not be an issue
With the custom caching you could technically make a collection that auto removed the properties you don’t want. I highly recommend against doing this however, it seems like a lot of extra overhead for not much gain. You’d be much better off using intents to reduce the amount of events received (inherently reducing cache size) and after that PR adding noop caches to the things you still get and don’t want to cache.
yeah, that was my Idea, I did it for the ChannelCache and it works fine.
It saves the Discord Rawdata, where some keys will be deleted and sets them in a map and when the get function is called it refills the object with a example Data-set and transforms it to a Discord.js Structure.
That's perfectly fine to do, just know you won't get much support here doing it that way
ik, it breaks some discord.js functionalities, some api methods requires some more data than just a Id
@wild flax since im not adding a function, what exactly do I need to test? https://github.com/discordjs/builders/pull/5#pullrequestreview-698625375
just making sure they return what they should return
that wasn't done for TimestampStyles though ?
But we are losing 6.67% coverage if we don't
I have no clue how to work with jest, specially when not using functions, are there docs that I can check or something?
would it just be expect(Faces.Shrug).toBe('¯\\_(ツ)_/¯')
why is it marked optional when the options param for MessagePayload#create is required? 
isnt this type (FileOptions[]|BufferResolvable[]|MessageAttachment[]) kinda misleading
(in BaseMessageOptions)
MessagePayload#resolveFile takes BufferResolvable|Stream|FileOptions|MessageAttachment so shouldn't it be (BufferResolvable|Stream|FileOptions|MessageAttachment)[]
each file is resolved individually
yeah theres been a few union types like that to be fixed
in APIRequest.make():
body = new FormData();
for (const file of this.options.files) if (file && file.file) body.append(file.name, file.file, file.name);
if (typeof this.options.data !== 'undefined') body.append('payload_json', JSON.stringify(this.options.data));
should i add a dontUsePayloadJSON field to override it and add each data field separately
or just abuse files instead of using data
Isn't it fine how it is? I thought you were just changing a docstring
no this is for stickers impl
the docs thing is just something i noticed lol
anyway ive been working on it and
trying to force it into files is way too much trouble ```js
DiscordAPIError: The browser (or proxy) sent a request that this server could not understand.
Okay, I tested the new CacheFactory/Cache Manager
and what I can say that they are some Problems, which should be fixed.
When capping the Collections to a specific limit, some Problems are created
In less words: You wont receive Events for the uncached Structures
I capped the cache of the ChannelManager to 10
This caused, that I didnt recieve this Events:
MessageCreateChannelUpdate
-> Nearly every Channel related Event, which requires the Cache...
When uncapping the Collection or trying it on a cached Structure, you receive the Events as usual.
it's generally not recommended to limit the guild or channel cache because of how d.js works
keeping them cached is not heavy on memory usage, that's stuff like messages/presences/etc
Not receiving events for uncached structures is definitely intended, which is also why partials exist
Yeah for Interfaces and user facing text it’s probably better
Discord's API docs also use a mixture of ID and id but never Id from what i can see
Enabled all Partials , but not receiving the Events, when the Collection is capped. When uncapped => works
const {token} = require('./config.json')
const Discord = require('discord.js');
const client = new Discord.Client({
intents: ["GUILDS","GUILD_MESSAGES", "GUILD_MESSAGE_REACTIONS"],
partials: ['MESSAGE', 'CHANNEL', 'REACTION', 'USER', 'GUILD_MEMBER'] ,
makeCache: Discord.Options.cacheWithLimits({
ChannelManager: 1, //
}),
});
client.on('ready', ()=>{
console.log(client.channels.cache.size)
})
client.on('messageCreate', (message) => {console.log(message.channel)})
client.login(token);
It’s not like we orientate our code standard based on discord’s :P
thought you did ¯_(ツ)_/¯
Hell naw
We don’t even know what they use internally
And we surely won’t start using snake case just because their API is in python/flask

yeah thats true but I think the public stuff should serve as reference
And you still based your names based off of theirs for example I asked for ephemeral (which is the worse name they've come up with) to be changed and I was told it wouldn't because that's what Discord uses
(btw Rodry, I updated my comment about URL's casing)
ah I didn't see it, lemme look
I see but why is that the case on that specific scenario?
like for example, doesn't displayAvatarURL fall under the "joined with other words" category?
or does that only apply to interfaces and classes
@solemn oyster ^^
I'm a bit mixed in that regard
I agree displayAvatarURL looks good, the problem comes when it's an <Acronym><Word>, like URLIdentifier
is that used anywhere? Never seen it
Either way it's a different issue, and 6036 will exclusively change the casing of ID, and nothing else
It's an example
ah I see
tbh im not against nor in favor of this change, it just seems like something so small that's gonna require so many changes that it's barely worth it imo
The URL or the ID one?
ID
If you ask me, this was the best moment to do it
We haven't been below 15 PRs for 3 years or so, and we had plans to change ID to Id with the TypeScript rewrite
Tracking the breaking changes in the TS rewrite with that mixed in... 
ah well in that case then yeah sure
and this change isn't as controversial as structures (which tbh i was surprised with the backlash, i didn't even know they existed) but yeah if you were planning on doing this anyway, v13 is the best time to do so
We're getting closer to the release right? I saw some pinned issues be closed the other day so i thought it could be near 👀
We'll probably link this comment if somebody complains about the [Structures] change https://github.com/discordjs/discord.js/issues/6039#issuecomment-873621116
christ that's huge, lemme look
I guess message partials are more unique, you need the channel cached in order to even get them
imo URL should be changed along with ID, both are always spelled in uppercase, one being an acronym doesn't seem that relevant
google style guide for java/js specifies it should be userId, iconUrl
yeah, that means that the new Cache Manager is nearly useless. (Except on Messages & Precenses)
It's not really
Your case is just obscenely obscure
Because at this point why do you even use a library at all?
sorry, when I sound rude.
But could I/someone do a Pull Request on the Guide and make a big Note, that Capping Channels, Roles, Guilds will break the whole Library?
We already have this issue pinned: https://github.com/discordjs/discord.js/issues/3924
It could probably be extended to mention caches
Is there going to be an alternative explanation for what to use in place of structures? Seems like there's going to be a lot more complaints
my PR has what's recommended
otherwise, defineProperty
https://github.com/discordjs/discord.js/issues/3924#issuecomment-656429545
Are there any proposals in this comment that have not been made?
customId and options shouldn't be optional, any reason why they are marked as such here?
If anything the first point.
I think this is better, I don't know if it would be possible but something like this in the documentation specifying in each event which intent and cache is required and necessary to work would be great
I'm thinking of doing that and making a pr, but I'm not sure whether to add something like <info> This event requires the GUILD_MEMBERS intent.</info> or just add it to the jsdoc description without <info>
Because it's used in the constructor of MessageSelectMenu where you don't need to set all the properties. You can set something in the constructor and then use method later to assign other properties
ah true I guess, but then the docs become misleading on the typedef
Docs dont need to perfectly represent the types
Those structures will probably move to /builders anyway
Would conditional nulling types be beneficial? If so, I could open a pull request...
Definitely could be, though that seems like a huge undertaking to apply across the lib
I can find docs on the Ternary type modifier, do you have information for it?
Ah, right, sorry. That's custom. Here's the impl:
/**
* Conditional typing extension helper.
*
* 1. If `T extends SUPERTRUTHY`, then `TRUTHY`
*
* 2. If `T extends SUPERFALSY`, then `FALSY`
*
* 3. Else `FALLBACK`
*/
export type ExtendConditional<T, SUPERTRUTHY, TRUTHY, SUPERFALSY, FALSY, FALLBACK = never> = T extends SUPERTRUTHY
? TRUTHY
: T extends SUPERFALSY
? FALSY
: FALLBACK;
/**
* Ternary helper function for typing.
*/
export type Ternary<FLAG extends boolean, TRUTHY, FALSY> = ExtendConditional<FLAG, true, TRUTHY, false, FALSY>;
Could be changed around, etc. to be easier to include in djs
Would also resolve issues such as this, by defining type Client<LOGGED_IN> = Ternary<LOGGED_IN, LoggedInClient, BaseClient>, etc.
! solves that as well
I mean there's some styling inconsistencies here but that's easily fixed, I think this is more about if we would want to do this in the current version (which is just JS + a typings file) vs leaving it for the TypeScript rewrite
no, bad
client.user will be there in the events though (obviously assuming that there is client at all, but in such case it would never be there anyway)
optional chaining is preferred over not-null assertions
I'm new to this project; what's the plan for a ts rewrite?
Ah I see
@copper laurel What about something like this?
type Ternary<V extends boolean, T, F> = V extends true ? T : V extends false ? F : never;
type Nullify<T> = { [P in keyof T]: null };
type ConditionallyNull<T, V extends boolean = boolean> = Ternary<V, T, Nullify<T>>;
class BaseClient {
foo: number;
}
interface LoggedInClient {
user: object;
}
export type Client<LoggedIn extends boolean = boolean> = BaseClient & ConditionallyNull<LoggedInClient, LoggedIn>;
LoggedIn extends boolean would match our casing conventions unless theres a need for that format?
Otherwise yeah that looks in line with our style
no = boolean?
Oh yeah thats fine
I'm only picking on styling, not functionality
@wild flax @tacit crypt @slate nacelle @solemn oyster is this sort of conditional typing something you want to go for?
Probably also @neat bolt because typings wizardry
is this the thing where you do the thing
with the null stuff after login
i'd rather just this if at all
class Client<LoggedIn extends boolean> {
always: number;
sometimes: LoggedIn extends true ? number : null;
}
also would apply to a lot of other objects as well such as messages (guild/dm) and interactions (guild/dm)
seems like theres two different proposals here then
- a generic that changes the type based on the state of the object in time
- a generic that chooses which variant of some concept to use
im ok with the former, though it will require very careful consideration that the typestate is valid
im against the latter, those should just be two separate declarations, or if applicable, inheritance
its just error prone due to the type machinery you have to do, bad for documentation for similar reasons, and is just laziness over explicitness for not much gain
@bitter peak @copper laurel
This is how prisma does some of its typings, especially related to rejectOnNotFound. We could possibly look into that maybe?
above comment 
Question: If in https://discord.com/developers/docs/resources/user there is a way to get the nitro subscription, why don't you put it in user object? Or it isn't possible?
isn't interaction.guildID just a shortcut method for interaction.guild.id?
That property is only provided through OAuth2, not to regular bots
Which is why discord.js does not support it
Coz if so, i dont see why it would be needed
Ah alr thanks
Interaction#guildID is a property that holds the interaction guild ID
Interaction#guild is a getter that relies on the first property (equivalent to <Client>.guilds.resolve(<Interaction>.guildID)
The two properties exist because you may get a guild interaction from an uncached guild
Leading guildID to hold the correct guild ID... but guild to be null
Should not happen as long as the client user is in the target guild, and you enabled the GUILDS intent, and not messing with cache but you shouldn't do it in anyway
ah i see
In OAuth2 that isn't very useful, at least in my opinion. If I was discord I would add it to the api it self not to OAuth2
thanks fot the explanation
They purposefully did it so we can't get that information without explicit consent from the user
OAuth2 requires the target user to say "Yes I want to give my profile information to that thing" while regular API doesn't
It won't happen, at least not in a near future, it already took a while for badges & co. to be available to bots
The original reason was to prevent "nitro-only" features that would break equality between regular and Nitro users for non-Discord related stuff
I see, thanks for your detailed explanation in this topic.
I know this change was made long ago but why don't ClientUser#setActivity , ClientUser#setAFK, ClientUser#setPresence and ClientUser#setStatus return promises anymore?
Because they are gateway commands and I don't think there is anything async in these
^
Maybe that should be mentioned in the v13 changes guide?
wait i'm confused
would't the custom / commands be a thing at v13 ?
if so why do i already see /commands at the https://discord.js.org/#/ and in the server here aswell ?
not sure if this is the right channel
yeah thats what i mean
I don't think anyone benefits from knowing "why" is isnt a promise anymore
Some people might be interested
yeah idk where that comes from but it won't be incorrect for too long I think
Because the home page has been updated ahead of 13.0 release (since the documentation revamp)
And some bots here use the development version
Is this still true? (v13 changes guide)
wierd, wonder why, anyways thx
Looks like it falls back to a function always returning true
https://github.com/discordjs/discord.js/blob/master/src/structures/interfaces/Collector.js#L46
yeah so it wouldn't return a type error since the whole point of moving the filter to the options object was to make it optional right?
Hello fellow developers 
If I want to contribute to developing discord.js, where should I start?
🙏
Since Structures are removed from djs v13, how can I get the raw API response data (e.g. guild avatar for GuildMember) from Discord API?
by waiting for guild avatars to be merged
Thanks, I just needed a direction to extend.
Yeah, I got it. I used client.api before. I forgot about it. I used Structures for all new APIs like buttons/select menus etc in djs v12 so I got used to it. Thanks for the help!
I could get started on a PR for this if wanted, then
In my opinion this can be a very good addition to improve the typing. It would solve some problems.
Yeah. I think there are still some things about Typings that can improved and this is one of them
After v13 finishes what do you plan on current library because of discordjs-modules what will be the priority like is major semver prs gonna get accepted in current lib
@vivid field after the typings rewrite, calling .send on a PartialDMChannel throws an error saying the function can be null on typescript when it shouldn't, do you know how to fix this or why this is happening?
Do you think it's possible to change the property partial to function isPartial(): this is Partial... (for example <User>.isPartial(): this is PartialUser) to improve typings ?
would that really make send become null?
i searched through the entire file and i could not find a reason as to why that is because its all the same as it was before
Yeah
also why change from any to unknown?
because its generally better to use unknown
but you can't reassign a type to an unknown value
spread function annotations shouldn't be switched though, so that was just a mistake
I'm going through it already, except if you got the PR ready now
i think i got it all ready
only had to replace all ...args: unknown with ...args: any
and hasParams i think too
gotta be careful with that unknown/any change
Single args break that too, so basically any callback parameter
always think about subtyping and variance 
so like this too?
actually those shouldn't even be unknown, doesn't discord-api-types have those?
generally if it produces a value, you want unknown, if it consumes a value you want any
and also because nothing extends unknown, any time you do a conditional with unknown itll always be false
this can be correct sometimes, whats the function 
that doesn't actually appear anywhere tho so its just the ...args change
There's no actual function for that, just an example I tested
oh
but yeah just follow this 
Same error as with rest parameters
well yea, thats def wrong
youre basically assuming an unknown is Message
which is kinda against the whole point of it
im kinda surprised that works with any tbh
they should both fail
Well yea because any disables practically all type checking
So anything is assignable to it and any is assignable to everything
everything is any in TS until you explicitly type it
yep, if you want to be completely correct there, as in cb can be called with anything, then unknown is actually correct
so it makes sense that it works
i should write a blog on subtyping and variance in ts
Use generics:
declare function fn<T>(cb: (args: T) => void): void;
fn((message: string) => null);
thats actually the same as any
or rather, its the same as nothing at all
fn can't produce a value of T because it doesnt know what T is
so cb can't be called, ever
fn knows its string from inferring
no it doesnt
#6057 in discordjs/discord.js by ImRodry opened 13 seconds ago (review required)
types(*): change spread function args to any
📥 npm i ImRodry/discord.js#types-any-spread
i think that's all right?
the caller specifies that it is string, but at the body of fn, all it knows is T
go and try to implement that function yourself and you'll see
@outer raven i'll leave some comments
alright ty
bleh, easier here
for the setInterval and stuffs, do something like
foo<T extends any[]>(f: (...args: T) => void, ...args: T)
what difference does it make?
i actually had the last args as any[] but changed last minute cuz i thought they were wrong lol
the difference is the generic
now the stuff you receive in the callback is the same as the stuff you pass to the function
that was my initial thought. you can handle that T in your fn body
are you talking about the setInterval or the stuff earlier
pushed
maybe i misunderstood. i came later and just commented on the screenshot only without readin' above.
ya this thing?
yeah
a generic doesnt work there as i said earlier

very simply:
function fn<T>(cb: (args: T) => void): void {
cb(???);
}```
so the type makes no sense
yeah
It does, L1403, L1409, L1820 and L1821
There's also a last unknown at L4312 that I think also needs to be changed
are the first four actually any or should they be unknown, like i said earlier
4312 needs to be changed yea
The first four are what I showed above
you want the user to be able to assume the type?
With the single unknown param in the callback
It should be treated the same as unknown rest params in a callback, no?
no
if its any, any function type works
if its unknown, they have to type it as unknown and cast explicitly
(arg: unknown) => void and (...args: unknown[]) => void should both be any from what I can see
not always

it depends on what theyre used for
for example to check if something is a function, T extends (...args: any[]) => void is correct
to say that a function can be called with unknown value(s), cb: (...args: unknown[]) => void is correct
But most of the changed stuff is the latter example
Because unknown[] doesn't seem to work for callback parameters
how so?
function f(c: (a: unknown) => void): void;
f((x: unknown) => typeof x === 'string' ? ... : ...);
if you mean to say that the user knows what the type is and they can assume their types are correct then a: any
If we were to fix only the extends issue, that would be maybe 3 changed lines, the rest is just so you can do f((x: Message) => ...)
so yes?
I.. think so yea
depends what yall wanna do 
I'm not really opposed to keeping that as unknown there, just saw some people having problems with it
i.e. <#djs-help-v14 message>
it looks like those might be served better by generics?
there are plenty of breaking changes already, why make the message listener deprecated instead of just removing it altogether 
oh, is there not a type for message collector? @vivid field
There should be
Because it breaks the 100% of bots
Oopsie i swear i went through all unknowns and didn’t notice, will fix
i'd say for events and such, you should go with unknown
users can augment the interface to add their own events
and if they use a non-literal event name string, they should get unknown
but depends on what the other guys think
Sounds good to me
@wild flax what do about unknown/any in callbacks
just keep any
you heard the man 
Then the PR should be fine as-is I think
you gotta make a new pr for messagecollector
Couldn't that also be handled by the collector generics?
i dunno
Or is there none for that
i didnt read the whole thing 
Same tbh
Yeah the params for the collect/dispose events seem to be the same as the ones passed to the filter
@zenith oracle read this whole channel 
So I can probably just do the same thing there


does @discordjs/the-big-3 actually do anything on github?
also who are the big 3 I thought there were 4 lol
early responders, which is usually kyra, me and vlad
but will it tag you?
yeah
space is emergency responder 
I'm working on separating Interaction into Interaction and GuildInteraction for typings; where the latter has the guildId and guild properties always set, and the channel is a GuildChannel. Is this pattern okay and how should this be inherited by subclasses of Interaction?
Where/who do I complain to about all the dumb changes v13 has?
@neat bolt
oh uh
i think we should let typings somewhat reflect the actual code
dunno, can you give a sample
I didn't see a response during the discussion so I'm reposting my message XD
sounds reasonable at a glance
hm, maybe in that case would a generic to modify the properties be okay in this case? I know you said you were somewhat against it, but what about this:
type If<T extends boolean, A, B> = T extends true ? A : B;
export class Interaction<InGuild extends boolean = boolean> {
public readonly channel: If<InGuild, Channel, PartialDMChannel | null>;
public channelId: If<InGuild, Snowflake, Snowflake | null>;
public readonly guild: If<InGuild, Guild, null>;
public guildId: If<InGuild, Snowflake, null>;
// ...
public inGuild(): InGuild;
}
export class CommandInteraction<InGuild extends boolean = boolean> extends Interaction<InGuild> {
public readonly command: If<InGuild, ApplicationCommand<{ guild: GuildResolvable }>, ApplicationCommand | null>;
public readonly channel: If<InGuild, TextChannel | NewsChannel | ThreadChannel, DMChannel | PartialDMChannel | null>;
// ...
}
@neat bolt
uhh
maybe, maybe not
needs more thinking about
here's one improvement though, type If<T extends boolean, A, B> = T extends true ? A : T extends false ? B : A | B since the last case is T = true | false
ah right ty
@tacit crypt we had a whole discussion on why things should be any in certain places 
Can't be unknown*



