-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement app subscriptions #111
base: master
Are you sure you want to change the base?
Conversation
Snowflake applicationId, int limit = Discord.Limits.Rest.FetchEntitlementsPageSize, | ||
Snowflake? userId = null, Snowflake[]? skuIds = null, | ||
Snowflake? beforeId = null, Snowflake? afterId = null, | ||
Snowflake? guildId = null, bool excludeEnded = false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if before
and after
here are mutually exclusive since it's not documented and I have no way to test it. Hence, I'm not using fetch direction here, would require someone with a verified bot to test it.
Ideally userId
and guildId
should also be mutually exclusive and we would use ownerId
and ownerType
, similar to the json parameters used by the Create Test Entitlement endpoint. However, once again there is no documentation specifying such, so I've let it be as is.
Purchase = 1, | ||
|
||
/// <summary> | ||
/// The entitlement was a part of a Discord Nitro subscription. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not so sure about this description, the docs aren't very clear about it.
Description
Implemented SKUs and Entitlements as a part of App Subscriptions.
Changelog Ref:
Checklist