Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please describe the changes this PR makes and why it should be merged:
This PR adds the ability inside discord.js to manage guild integrations, from fetching them to editing and deleting them. It also adds a new structure:
Integration
, for a better OOP management (integrations are fairly complex: structure).Full documentation for integrations: https://discordapp.com/developers/docs/resources/guild#get-guild-integrations
Edit:
Turns out there is a
GUILD_INTEGRATIONS_UPDATE
event: https://discordapp.com/developers/docs/topics/gateway#guild-integrations-updateThis has been implemented in this PR too.
Question: In the first commit, I have covered everything the API support minus creating integrations since we do not have aResolved by creatingIntegrationStore
(and since they're not provided during ready nor when fetching the guild, only when we fetch the integrations), should I add ancreateIntegration
method in theGuild
class to cover this?Guild#createIntegration
.Semantic versioning classification: