Add app_permissions

[shaydewael]

Adds changelog and updates docs for new app_permissions field

[Zoddo]

Too sad this was insta-merged. 😞 I think this would have been a better wording, and consistent with how this is named everywhere else:

Suggested change

Interaction payloads now contain an `app_permissions` field whose value is the computed [permissions](#DOCS_TOPICS_PERMISSIONS/permissions-bitwise-permission-flags) for a bot or app in the context of a specific interaction (including any custom permissions for the origin channel). Similar to other permission fields, the value of `app_permissions` is a bitwise OR-ed set of permissions expressed as a string. Read details in the [interactions documentation](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-object).

Interaction payloads now contain an `app_permissions` field whose value is the computed [permissions](#DOCS_TOPICS_PERMISSIONS/permissions-bitwise-permission-flags) for a bot or app in the context of a specific interaction (including channel overrides). Similar to other permission fields, the value of `app_permissions` is a bitwise OR-ed set of permissions expressed as a string. Read details in the [interactions documentation](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-object).

[shaydewael]

I have another change coming up so I'll include this wording update. With changelogs, I'm mostly trying to get them deployed as fast as possible so I can post in DDevs, Github, etc.

[ImRodry]

Thanks for adding yet another feature with 0 prior warning!

[shaydewael]

@ImRodry It's an additive change so it won't break any apps—it's solely giving apps more information.

We also talked about the change in the latest DDevs event.

[ImRodry]

@ImRodry It's an additive change so it won't break any apps—it's solely giving apps more information.

We also talked about the change in the latest DDevs event.

Usually stuff is added and only announced a few days later to allow libs to implement the feature, otherwise not many people can use it at the official launch

[DonovanDMC]

@ImRodry It's an additive change so it won't break any apps—it's solely giving apps more information.
We also talked about the change in the latest DDevs event.

Usually stuff is added and only announced a few days later to allow libs to implement the feature, otherwise not many people can use it at the official launch

So you would rather it be announced and made usable in a few days?

[ImRodry]

No I'd rather it was done the opposite way: made available in the API and PR made and announced a few days later

[nickelc]

The docs say that app_permissions? is a string but it's an integer in the payload I'm receiving.

[braindigitalis]

If only messages had this too, we wouldnt need to cache roles at all for a lot of usages...

[shaydewael]

The docs say that app_permissions? is a string but it's an integer in the payload I'm receiving.

this is a bug, and shall be fixed momentarily! sorry about that

[DonovanDMC]

No I'd rather it was done the opposite way: made available in the API and PR made and announced a few days later

Why have it available and undocumented when it can be documented as it's made available

[ImRodry]

If a PR is made by a team member it’s documented so libraries can implement it. Releasing like this means thousands of people will rush into support servers asking where is the support for that new feature when it most likely will take a while to come out

[advaith1]

there is no reason for support for this feature to take a while to come out

[zeylahellyer]

The docs say that app_permissions? is a string but it's an integer in the payload I'm receiving.

this is a bug, and shall be fixed momentarily! sorry about that

A fix for this is now out on stable. As an aside, this PR isn't the right place to discuss procedures around feature release announcements