Jakob Helgesson svemat01

The Great Vitest Mocking Mystery: A Tale of Pain and Redemption

The Problem (aka "Why Am I Even a Developer?")

Picture this: Your tests were working perfectly fine. Life was good. Then you innocently add ONE import from cloudflare:test to your setup file, and suddenly ALL YOUR MOCKS ARE LYING TO YOU. They exist, but they do nothing. They're like ghost mocks, haunting your codebase with their useless presence.

// The import that ruined everything
import { env, applyD1Migrations } from "cloudflare:test";

Components

Train Task (DATA)

The data for what action should be taken by the system. Exists in two different types, collection and delivery.

Collection

Contains the station name and a rough estimate of how many items are going to be picked up.

Delivery

Contains the station name and a list of items to be picked up

Example type implementation

AutoComplete DJS v13.3.0

What is autoComplete?

"Autocomplete is basically choices but dynamic. every time the user presses a key in an autocomplete option, the bot gets an event and it can respond with what strings it wants discord to display as choices instead of having the choices be static." - Urcute#3119 on Discord

How do we use it?

For this guide, our command will be named autocomplete, this is not some built in command.

Prepare option for autocomplete

Before we can start to recieve autocomplete events on an option, we have to actually tell discord that we want it.

	{
	"description": "Caps Lock → Hyper Key (⌃⌥⇧⌘) (Caps Lock if alone)",
	"manipulators": [
	{
	"from": {
	"key_code": "caps_lock",
	"modifiers": {
	"mandatory": [],
	"optional": ["any"]
	}

	import { Interaction } from 'discord.js';

	import { slashCommands } from './SlashHandler';

	export const autoCompletes = slashCommands.filter(
	(command) => command.autoComplete
	); // Auto load commands from SlashHandler but only include them if they have an autocomplete function

	export const handleAutoComplete = async (
	interaction: Interaction