Make bot scope also include applications.commands by default

[Andre601]

I feel like that the bot scope should also include the rights/settings for the applications.commands one.

Why?
Well, with Slash commands becoming pretty much mandatory for verified bots in 2022 is the applications.commands scope a pretty much-required scope, so why not just include it into the default bot scope?
I can imagine many devs out there having an old bot invite somewhere that they forgot about and that still only has the bot scope, and with Discord not offering an automatic inclusion of the other scope can cause bots to break left and right.

So, since the slash command swill be pretty much required from 2022 onwards would it be somewhat pointless to have this separate scope to begin with and instead include its functionality into the main bot scope...
This could also be a good fix for #3552

[N1C0exe]

They have already say that this function will be implement ( source Discord Dev server from kadybat#0001 a discord staff )

[Andre601]

Well... At least something I guess

[viral32111]

Automatically included with the bot scope sounds fine, but it should still be kept as a standalone scope for slash-command only applications (i.e. ones without a bot account). They are very useful for when you don't need to use the bulk of the Discord API itself, such as just fetching data from third-party APIs and returning it in the interactions response.

[ckohen]

This seems like the wrong direction to go, there are plenty of legitimate reasons for bot owners or server admins to not want slash commands from a bot (and any future interaction types that fall under this scope).

Besides, including a scope by force is not how OAuth is designed, the url should clearly indicate what scopes are being requested.

[advaith1]

This change happened on July 11; should be marked as answered