Lot of ugly console.log statements out there. Not sure if debug is the right choice to use, but should grab a lib and make the log statements generally better

Would be good to use forms instead

Need to make sure to run it on the existing code as well

Real title should probably be "Embed constructor doesn't allow omitting the options parameter"

Describe the bug

When creating a new button, you have to manually set the options to null, otherwise TS will give you an error.

To Reproduce

import { Command, Embed } from "interaction-kit";

export default new Command({
    name: "embed",
    description: "Sends an embed",
    handler: (interaction) => {
        interaction.reply({
            embed: new Embed().setTitle("test"), // Error occurs here
        });
    },
});

Additional context

• interaction-kit V 0.1.1
• TypeScript

Solution (by @ThaTiemsz):

-    constructor(options: EmbedDefinition | null) {
+    constructor(options?: EmbedDefinition) {

in https://github.com/IanMitchell/interaction-kit/blob/main/packages/interaction-kit/src/components/embed.ts#L27

Need to figure out names and which are needed, but something like "beforeInteraction" and "afterInteraction"

This command should take in optional arguments and prompt for the rest, and then scaffold a new app. The options should look like this:

• --server - Development Server ID
• --token - Bot Token
• --public_key - Bot Public Key
• --application_id - Bot Application ID

Any options not passed in should be prompted during the process (if someone passes in an empty string, we should allow it and clearly explain where to get the value and where to add it later).

The file structure should look like this:

application/
├─ node_modules/
├─ src/
│  ├─ commands/
│  │  ├─ ping.js
│  ├─ index.js
├─ .gitignore
├─ .env
├─ package.json
├─ README.md

Describe the request
Context Menus were introduced a few days ago, and I think interaction-kit should support them.

Example Usage
N/A

Additional context
N/A

create-ikit-app should have a functional template for TypeScript

Not sure how best to make it work with typescript, but will be good to have around

These are pretty hot right now, would be good to have an example project for them

Vercel does not support Node 16 because AWS Lambdas don't 😭

If it works for our usecase, why reinvent the wheel?

For starters, let's get it executable and bundled as part of the package

All of our public methods and fields should have documentation on them

Right now if a bot sends a message with a button, then the instance dies, and a user clicks a button, Interaction Kit doesn't know what to do with it. Right now we lazily instantiate that list, as users run commands. We need a way to instead load this list on boot, for the most part.

Doesn't auth correctly

We might need these for some of the messages functions

#54 (review)

We have a rough Class / API setup for them, but they aren't currently integrated at all. They need to be added to the serialization methods and tested

devcontainers are pretty neat!

Describe the request
Forms (Modal Interactions) seem like a cool feature, and I think interaction-kit should support them.

Example Usage
no clue

Additional context

• Still unreleased
• https://devsnek.notion.site/devsnek/Modal-aka-Form-Interactions-e839b3dd8c214eb08f950764a8328e36

Delaying this functionality a bit to speed up alpha 1. We'll want to auto-update the command handlers when a file is saved, and also take a look at the command signature - if it's changed, we should fire an update event.

@ckohen said that it took some time in the actions

Oops, trout.js and deschtimes.js weren't supposed to make it into the repository.

We don't currently support these, and we should

Add a small section in the readme explaining the differences between the gateway and HTTP api, and compare the advantages / disadvantages of both to help people who are new to this topic / don't know why something isn't working as they thought it would be.

We need to move it into a process we can kill instead of using a cached import that never refreshes

I need to come up with a list of API routes to put here

• Something
• Else

I love Prisma, you love Prisma, we all love Prisma. Let's show the world how Interaction Kit loves Prisma.

After things settle down a bit, I want to audit the dependencies and see if anything can be removed or updated - I know we get a lot of deprecated warnings on install right now

There are a bunch of TODO comments for adding validations to our library - we can ship some alphas and betas before adding it, but we should have these in before v1

I also want to revisit Vlad's djs types library and see if it's an appropriate replacement, same thought as djs/rest.

Describe the bug
When attempting to start up, an error is thrown immediately if the --es-module-specifier-resolution flag is configured incorrectly.

To Reproduce
1.) Start an app using interaction-kit without the --es-module-specifier-resolution flag set to node in the run command.
2.) Observe the "cannot find module '.../node_modules/interaction-kit/dist/data/snowflake'" error.

I like the idea of having several ready-to-go commands available, but I'm not sure I love having a README embedded in them like that. Renaming it to starter-kit with a README and a commands directory feels less clear, though (although it does give flexibility to do more with it). That said, we also have the examples directory for more complex things. Not sure what I want to do with this yet - anyone have thoughts?

Would be nice to have a GitHub action handle the package publish flow. Need to look into how that works with TypeScript too

Doesn't need oauth or anything, although that might be nice for a follow-up example.

I really like how Next.js has a tons of examples right in the repo that you can deploy and test - I think this is a pattern that would be useful here (to a more limited extent).

Serverless slash commands have seen a lot of community interest, so having an example on how to build and deploy one would be really useful.

This is two-parter, and probably more of a discussion.

1. Gotta add tests to the main library at some point - probably once the core API design is hammered down a bit.
2. I would love to have some sort of Jest plugin to help developers test their code. Maybe more of a e2e-targetted system as opposed to unit testing? Not sure how best to do this, but jest-discord gets a lot of traffic and having something like that from the get-go would be awesome.

Describe the request
Currently, you can only have the commands registered on a single guild (specified in the .env).
It is not possible to use the same bot on multiple servers, which means that the library can't be used outside of testing.

Example Usage
One way to do it would be to set DEVELOPMENT_SERVER_ID to global, or by simple removing the variable from the .env entirely.

Additional context
N/A

Pretty cool feature

This will let us add some test dev-bots to use and keep our website in this repository too

We have a few ways of approaching API helpers - we could take each route and create a getRoleByID helpers, or we could create a standard Record interface that does something like this:

Role.fetch(id).edit({}).save()

Or something similar. It seems like people like this approach a little more, and we can easily build it on top of @leahlundqvist's API helpers and queue systems.

we are filthy

I don't love the current API

Describe the bug
Currently, interaction.options is typed as {}.
This causes TypeScript to throw an error (Property 'question' does not exist on type '{}').
Logging interaction.options to the console, you get {}.

Instead, it should be typed as

Record<string, string | number | boolean | User | Role | Channel>

To Reproduce

import { Command, StringInput } from 'interaction-kit';

export default new Command({
  name: '8ball',
  description: 'Ask the magic Eight Ball',
  options: [
    new StringInput({
      name: 'question',
      description: 'What do you want the Magic Eight Ball to answer?',
      required: true,
    }),
  ],
  handler: (interaction) => {
    interaction.reply({
      message: `> ${interaction.options.question}\n\n🎱 | Flip a coin lolol`, // TS error here
    });
  },
});

Additional context
I found the typings in node_modules\interaction-kit\dist\index.d.ts on line 459 , but I couldn't find them in the repository

Doesn't need to have much info on it to start

I'm not very good at these, but I would like these to have be as helpful as possible

This command should load up environment secrets using dotenv and then execute the "main" file of the package.json file. Some of this logic will exist in the package itself rather than the cli, but the goal of this command is to enable command hot-reloading and auto-updating in the development server and output helpful log messages.

🎉 buttons are out! Let's add support for them.

We should validate they'll work with API constraints too.

If a package version is incremented, we should auto publish it