feat(PartialGroupDMChannel): add missing properties

[imnaiyar]

Please describe the changes this PR makes and why it should be merged:
Props Added:

• ownerId
• lastMessageId
• lastPinTimestamp
• lastMessage
• lastPinAt
• awaitMessageComponent
• createMessageComponentCollector

I noticed ownerId, last_message_id and last_pin_timestamp was missing from PartialGroupDMChannel. This PR fixes that.

While looking at the api documentation alone, it is hard to determine for me if the owner_id can be missing for Group DM Channel's, but from my testing so far, I found it to be always present. So taking that at face value

Status and versioning classification:

• Code changes have been tested against the Discord API, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
discord-js	⬜️ Ignored (Inspect)	Visit Preview		Dec 5, 2024 9:41pm
discord-js-guide	⬜️ Ignored (Inspect)	Visit Preview		Dec 5, 2024 9:41pm

[nyapat]

While looking at the api documentation alone, it is hard to determine for me if the owner_id can be missing for Group DM Channel's, but from my testing so far, I found it to be always present. So taking that at face value

owner_id? has been optional since before threads were added, I think you should leave it as such

[imnaiyar]

Yeah it's optional because it can be missing for other channel types, my thinking was it would always be present for GroupDMs, but now that you mention it, looking at other djs structures (ThreadChannel) it accounts for that. So I think I should stick to the library behavior

[imnaiyar]

I noticed last_message_id and last_pin_timestamp is also missing, I am wondering if it was left out for a reason or I should add those too

[vladfrangu]

I noticed last_message_id and last_pin_timestamp is also missing, I am wondering if it was left out for a reason or I should add those too

If they are returned, feel free to add them in your PR and update the title/description

[imnaiyar]

Added, awaitMessageComponent & createMessageComponentCollector, noticed them missing, but there was no issue on creating collector on group dm for components. I see no reasons to exclude it.

[vladfrangu]

Added, awaitMessageComponent & createMessageComponentCollector, noticed them missing, but there was no issue on creating collector on group dm for components. I see no reasons to exclude it.

Do these actually work 👀?

[imnaiyar]

Do these actually work 👀?

Yes, I've tested it. The channel object returned in the interaction payload contains the group dm's id, which is the most you would need for a channel component collector. At least I have not encountered any edge cases where it wouldn't work. As long as you have Channel partial, it should work

Resolved.