Current sync status with Discord API Docs PRs

[vladfrangu]

A lot of PRs are (still) open in Discord's API Docs repository, and some features may arrive that we don't have the types for yet Vlad from the future here: that isn't the case anymore
This issue is here just as a check list to make sure we are at least up to date with Discord

If any of these have been done already, let me know here, on Discord, and if not, feel free to either let us know here or make a PR!

Round 1

• Inline Replies discord/discord-api-docs#2118

• Document missing fields in Create and Modify Guild discord/discord-api-docs#1764

• Stickers documentation discord/discord-api-docs#2155

• Remove 3 guild integration endpoints which bots have been blocked from accessing. discord/discord-api-docs#2087 ?

• Document Discovery settings discord/discord-api-docs#1762

• Fix create invite target_user_id field and add public_flags to example user objects discord/discord-api-docs#1708

• Make guildmember premium_since not optional discord/discord-api-docs#2044

• 

• Document Member nick being optional discord/discord-api-docs#2209 ?

• Document last_pin_timestamp being nullable discord/discord-api-docs#2215

• Document Attachment dimensions being optional discord/discord-api-docs#2214

Round 2

• Re-organize interactions structure because 1 file is NOT enough

• Consider re-organizing all REST files based on their methods? so we'd do /rest/interactions/<method>.ts, where we define just that method's interfaces, respecting the current naming convention

• Oauth2 types. Are they even accurate? Nobody knows. Need to shoot an eye at those again, esp with all the scopes... Lord spare me

• Document Discovery settings discord/discord-api-docs#1762

• discord/discord-api-docs@77c3756

• discord/discord-api-docs@eed6084

• discord/discord-api-docs@2c9f178

• discord/discord-api-docs@0b2b84d

• discord/discord-api-docs@5afbad7

• Document APIv9. discord/discord-api-docs#2855

• Document JSON Error Code 30037 discord/discord-api-docs#2869

• Boopable Noses - Soon™️

[advaith1]

Re-organize interactions structure because 1 file is NOT enough

probably should wait until docs are updated & separated

[vladfrangu]

Re-organize interactions structure because 1 file is NOT enough

probably should wait until docs are updated & separated

This isn't really a need to wait for docs situation. And I doubt that'll happen soon, this is more of a comfort thing for us. My plan is to have a folder _interactions where I plop all enums in one file, all sent data in ine, all received data in another, etc

[advaith1]

ah, I meant like wait until slash commands and general interaction docs are separate and move those into separate files, that would probably make it cleaner