Added documentation to GatewayIntents.cs, GatewayClient.cs, ShardedGatewayClient.cs and GatewayOpcodes.cs

[Red-K0]

No description provided.

[Red-K0]

Fixed the brace

[KubaZ2]

What about using the see tag to mention events from GatewayClient instead of using the Discord raw event names?

[Red-K0]

What about using the see tag to mention events from GatewayClient instead of using the Discord raw event names?

I thought about it, but I couldn't seem to find any centralized way to reference them all without having to tag random members across NetCord. If it does exist, I'll use it though. (I could also add one)

[Red-K0]

To clarify on my last comment, I was referring to newer events such as polls.

[KubaZ2]

I would remove the polls intents from this pr and move them to #18.

[Red-K0]

Sure, moving them after I update the see tags then.

[Red-K0]

<see> tagged literally everything.

[Red-K0]

Added more documentation in the meantime, all events in GatewayClient should be covered now.

[Red-K0]

All bullet points converted to XML tags.

[KubaZ2]

• We should name guild members as guild users because NetCord's representation of a guild member is the GuildUser
• I think that all gateway events should have required intents specified.
• Some intents, like GuildPresences influence on other behaviours and I think that they should be documented for intents too.

[Red-K0]

Instead of being pedantic about it, added the suggestion, but fixed the casing of The to the.

[Red-K0]

Changed the documentation for it

[Red-K0]

We should probably try and finalize this soon

[Red-K0]

Added IPartialMessage changes.

[KubaZ2]

Could you also add xml docs for ShardedGatewayClient?

[Red-K0]

Sure