feat: Add GuildID field to the AuditLogEntry struct

[rwhelan]

Adds the field GuildID to the AuditLogEntry struct. While not documented (https://discord.com/developers/docs/resources/audit-log#audit-log-entry-object-audit-log-entry-structure) it is part of the struct sent on the wire:

[AbduAmeen]

I rely on this change so if we can get it merged soon, that would be great. Thanks

[rwhelan]

bump? This should be an easy merge

[rwhelan]

[FedorLap2006]

Sorry for leaving this without an answer for this much time.
We usually don't merge stuff if it's not in the API documentation.

There's currently an open PR for this, so moving forward with this PR will be only possible after that one is merged.

P.S. It should be noted there's also discord/discord-api-docs#5865, however it was closed a while ago.

[hhaste]

Sorry for leaving this without an answer for this much time. We usually don't merge stuff if it's not in the API documentation.

There's currently an open PR for this, so moving forward with this PR will be only possible after that one is merged.

P.S. It should be noted there's also discord/discord-api-docs#5865, however it was closed a while ago.

Does it really matter that much if it's "undocumented"? Seems like a no-brainer to approve this merge. I really doubt this field would be omitted in a future update - it's not like audit logs are a thing outside of guilds lol.

This event is pretty much useless if we don't know which guild the event is dispatched from. Kindly reconsider.

[rwhelan]

Sorry for leaving this without an answer for this much time. We usually don't merge stuff if it's not in the API documentation.
There's currently an open PR for this, so moving forward with this PR will be only possible after that one is merged.
P.S. It should be noted there's also discord/discord-api-docs#5865, however it was closed a while ago.

Does it really matter that much if it's "undocumented"? Seems like a no-brainer to approve this merge. I really doubt this field would be omitted in a future update - it's not like audit logs are a thing outside of guilds lol.

This event is pretty much useless if we don't know which guild the event is dispatched from. Kindly reconsider.

[hhaste]

@FedorLap2006 Several other libs support this feature, so there is virtually no reason not to merge this 🤔

JDA: https://docs.jda.wiki/net/dv8tion/jda/api/events/guild/GenericGuildEvent.html#getGuild()
Discord.JS: https://github.com/discordjs/discord.js/blob/main/packages/discord.js/src/client/actions/GuildAuditLogEntryCreate.js#L10
Discord.NET: https://github.com/discord-net/Discord.Net/blob/dev/src/Discord.Net.WebSocket/Entities/AuditLogs/SocketAuditLogEntry.cs/#L22
Discord.PY: https://github.com/Rapptz/discord.py/blob/0e016be42ca4f34bb89761261a1c7c12f4cc8c48/discord/types/gateway.py#L351

[hhaste]

Also @rwhelan - it is more appropriate to implement this field on the GuildAuditLogEntryCreate struct (events.go:406) rather than AuditLogEntry, since guild ID is only ever included from this particular gateway payload.