refactor(helpers): separate functions into files (#667)

* refactor(helpers): separate functions into files

* idk

* idk

src/helpers/commands/create_slash_command.ts

@@ -0,0 +1,31 @@
+import { applicationID } from "../../bot.ts";
+import { RequestManager } from "../../rest/request_manager.ts";
+import { CreateSlashCommandOptions } from "../../types/mod.ts";
+import { endpoints } from "../../util/constants.ts";
+import { validateSlashCommands } from "../../util/utils.ts";
+
+/**
+ * There are two kinds of Slash Commands: global commands and guild commands. Global commands are available for every guild that adds your app; guild commands are specific to the guild you specify when making them. Command names are unique per application within each scope (global and guild). That means:
+ *
+ * - Your app **cannot** have two global commands with the same name
+ * - Your app **cannot** have two guild commands within the same name **on the same guild**
+ * - Your app **can** have a global and guild command with the same name
+ * - Multiple apps **can** have commands with the same names
+ *
+ * Global commands are cached for **1 hour**. That means that new global commands will fan out slowly across all guilds, and will be guaranteed to be updated in an hour.
+ * Guild commands update **instantly**. We recommend you use guild commands for quick testing, and global commands when they're ready for public use.
+ */
+export async function createSlashCommand(options: CreateSlashCommandOptions) {
+  validateSlashCommands([options], true);
+
+  const result = await RequestManager.post(
+    options.guildID
+      ? endpoints.COMMANDS_GUILD(applicationID, options.guildID)
+      : endpoints.COMMANDS(applicationID),
+    {
+      ...options,
+    },
+  );
+
+  return result;
+}