Dasgo beta

[switchupcb]

Version beta (prior to v10) will require the following changes:

Flags Overhaul

• [x] Flags need to be re-reversed (unreversed) so that they are presented in the order FlagAuditLogEvents. This models how a user uses flags.
• [x] Certain fields that are supposed to be integers, were specified as Flag or CodeFlag.

Pointers (Specification)

• [x] The specification has been updated to better model the requirements of Dasgo. In short, Dasgo type fields need to be correct and we run into issues — during JSON marshal — when they are NOT. This entails determining how to best model the following Discord API Rule: https://discord.com/developers/docs/reference#nullable-and-optional-resource-fields.
• [x] The specification needs to be implemented.

This may require another update to the specification.

Query Strings

• [x] JSON Params need to be distinguished from Query Strings: This is because JSON parameters refer to data specified in the HEADER (JSON BODY), while Query String parameters refer to data specified in the URL (i.e ?thread_id=232341243). This can be as simple as renaming all incorrectly named Query String tags to url.

Image Data

• [x] The data type of image data fields need to be determined and reassigned accordingly.

  Image data is a Data URI scheme that supports JPG, GIF, and PNG formats. An example Data URI format is:

  data:image/jpeg;base64,BASE64_ENCODED_JPEG_IMAGE_DATA

  Currently, structs with image data fields are marked with // TODO (Image Data). It may help to review the changes using the documentation directly (via search).

[switchupcb]

We will keep Data URI schemes as strings unless it makes sense to create its own data type (as per https://onethinglab.com/data-url-parse-in-golang). It's a given that API Wrappers would implement decoding at the level of their own needs.