Command Middlewares

In Seyfert middleware are functions that are called before the command is executed. You can use them to do verifications, logging, etc.

Let’s create a basic middleware that logs in the command that is being executed.

Creating a middleware

logger.middleware.ts

import { createMiddleware } from "seyfert";

// The generic type tells the middleware what information it'll pass to the command
export const loggerMiddleware = createMiddleware<void>(
  (middle) => {
    // Log the command
    console.log(
      `${middle.context.author.username} (${middle.context.author.id}) ran /(${middle.context.resolver.fullCommandName}`
    );

    // Pass to the next middleware
    middle.next();
  }
);

Now let’s register the middlewares on seyfert but first we should create a file to export all our middleware

middlewares.ts

import { loggerMiddleware } from "./path/to/logger.middleware";

export const middlewares = {
    // The key is the name of the middleware which will be used to reference it on the command
    logger: loggerMiddleware
}

index.ts

import { ParseLocales, Client, ParseMiddlewares, ParseClient } from "seyfert";
import { middlewares } from "./path/to/middlewares";

const client = new Client();

// Register the middlewares
client.setServices({
  middlewares: middlewares
});

declare module "seyfert" {
  interface UsingClient extends ParseClient<Client<true>> {}

  // Register the middlewares on seyfert types
  interface RegisteredMiddlewares
    extends ParseMiddlewares<typeof middlewares> {}
}

Now we can use the logger middleware on any command.

ping.command.ts

import { Middlewares, Declare, Command, type CommandContext } from "seyfert";

@Declare({
  name: "ping",
  description: "Ping the bot"
})
// Note we are using the name "logger" to reference the middleware
@Middlewares(["logger"])
export default class PingCommand extends Command {
    async run(ctx: CommandContext) {
        await ctx.reply("Pong!");
    }
}

Now every time the ping command is executed, the logger middleware will log forward the command.

Note

Middlewares are executed in the order in which they are added.

Stop middleware

As we had said you can use middlewares to do verifications, and you can stop the execution of the command if the verification fails.

Let’s take a look adding some logic to the logger middleware.

logger.middleware.ts

import { createMiddleware } from "seyfert";
import { ChannelTypes } from 'seyfert/lib/types';

export const loggerMiddleware = createMiddleware<void>((middle) => {
  // Log the command
  console.log(
    `${middle.context.author.username} (${middle.context.author.id}) ran /(${middle.context.resolver.fullCommandName}`
  );

  // Check if the command is being executed in a guild
  if (middle.context.interaction.channel?.type === ChannelType.DM) {
    return middle.stop("This command can only be used in a guild.");
  }

  // Pass to the next middleware if the command is being executed in a guild
  middle.next();
});

Now every time the ping command is executed in a DM, the logger middleware will stop the execution of the command and send the error message to the handler. Learn how to handle errors here.

Note

Notice you can access to the interaction data using middle.context.interaction

On the other hand we could skip the interaction (ignore the interaction and literally do nothing) by using middle.pass()

logger.middleware.ts

import { createMiddleware } from "seyfert";
import { ChannelTypes } from 'seyfert/lib/types';

export const loggerMiddleware = createMiddleware<void>((middle) => {
  // Log the command
  console.log(
    `${middle.context.author.username} (${middle.context.author.id}) ran /(${middle.context.resolver.fullCommandName}`
  );

  // Ignore the interaction if it's a DM
  if (middle.context.interaction.channel?.type === ChannelType.DM) {
    return middle.pass();
  }

  // Pass to the next middleware if the command is being executed in a guild
  middle.next();
});

Passing data

The last thing we can do with middlewares is to pass data to the command. This can be useful to avoid repeating the same code in multiple commands for example fetching data from the database.

We’ll continue with the logger middleware and pass some data to the command.

logger.middleware.ts

import { createMiddleware } from "seyfert";

// This interface is used to let the middleware know what type of data to pass to the command
interface LoggerData {
    time: number;
}

export const loggerMiddleware = createMiddleware<LoggerData>((middle) => {
    // Log the command
    console.log(`${middle.context.author.username} (${middle.context.author.id}) ran /(${middle.context.resolver.fullCommandName}`);

    // Pass the data to the command
    middle.next({ time: Date.now() });
});

Now let’s modify the ping command to receive the data.

Note

If you want to pass data from more than one middleware you can use the | operator, for example CommandContext<never, "logger" | "otherMiddleware">

ping.command.ts

import { Middlewares, Declare, Command, type CommandContext } from "seyfert";

@Declare({
    name: "ping",
    description: "Ping the bot"
})
@Middlewares(["logger"])
export default class PingCommand extends Command {
    async run(ctx: CommandContext<never, "logger">) {
        const time = ctx.metadata.logger.time;
        console.log(time);
        await ctx.reply({
            content: `Pong! Time: ${time}`,
        });
    }
}