[Typing] interaction.followUp() should not have ephemeral in its options?

[Zer0xxxx]

Which package is this bug report for?

discord.js

Issue description

Currently, Discord.js allows to write this:

await interaction.followUp({ content: errorMsg, ephemeral: true });

(In my current code, interaction has the type: ChatInputCommandInteraction)

This has already been discussed here, and the "API limitation" concern is still relevant since I had the same problem today: #5702

Therefore, I think that the typing should invalidate the use of this option.
Current typing is misleading: it suggests that you can do a followUp with an ephemeral, whereas in practice this is not true.

Code sample

No response

Versions

discord.js : 14.15.3

Issue priority

Low (slightly annoying)

Which partials do you have configured?

Not applicable

Which gateway intents are you subscribing to?

Not applicable

I have tested this issue on a development release

No response

[Jiralite]

Current typing is misleading: it suggests that you can do a followUp with an ephemeral, whereas in practice this is not true.

Sounds like you are following up on a deferred response and assumed this to be not true. Follow-ups can happen after the initial response and may be ephemeral.

[Zer0xxxx]

Current typing is misleading: it suggests that you can do a followUp with an ephemeral, whereas in practice this is not true.

Sounds like you are following up on a deferred response and assumed this to be not true. Follow-ups can happen after the initial response and may be ephemeral.

Oh, okay!
Then, what do you think about this one? @Jiralite

It sounds like a type intersection is missing for this case.

[Zer0xxxx]

@Jiralite ?

[monbrey]

There's absolutely no need to ping someone twice in less than two hours.

I'd rather not have to split the type that followUp accepts based on a stateful parameter.

[Zer0xxxx]

There's absolutely no need to ping someone twice in less than two hours.

I'd rather not have to split the type that followUp accepts based on a stateful parameter.

There's absolutely no need to close an issue as not planned in less than 2 minutes. Especially when the issue is totally related to the SDK.
Peace.

[monbrey]

That is the answer though. We don't plan to change this.