Handling X-Audit-Log-Reason Header

[nateweisz]

Description of the Issue

We should either provide an interface like Auditable that has a function like withAuditLogReason or something like that. This should be decided one when the higher level api is implemented.

[surajkumar]

Related PR: #42

[surajkumar]

Possibly, we can add it as another optional field to the DiscordRequest objects and provide the value using the RequestBuilder classes that we have. We should create a list of all the endpoints that use the X-Audit-Log-Reason header.

[nateweisz]

Possibly, we can add it as another optional field to the DiscordRequest objects and provide the value using the RequestBuilder classes that we have. We should create a list of all the endpoints that use the X-Audit-Log-Reason header.

Hi, haven't been active on this project recently since I've been pretty busy but I've got an idea. We can make an IAuditable or something and just check if the request is an instance of it, unless that would be hard to implement into the builder's.