Action schema registered via addActionSchema(). Defines event handler implementation and lifecycle callbacks for state management integration.
Actions provide a way to attach custom event handlers to strategies for:
Each action instance is created per strategy-frame pair and receives all events emitted during strategy execution. Multiple actions can be attached to a single strategy.
import { addActionSchema } from "backtest-kit";// Define action handler classclass TelegramNotifier implements Partial<IAction> { constructor( private strategyName: StrategyName, private frameName: FrameName, private backtest: boolean ) {} signal(event: IStrategyTickResult): void { if (!this.backtest && event.action === 'opened') { telegram.send(`[${this.strategyName}/${this.frameName}] New signal`); } } dispose(): void { telegram.close(); }}// Register action schemaaddActionSchema({ actionName: "telegram-notifier", handler: TelegramNotifier, callbacks: { onInit: async (strategyName, frameName, backtest) => { console.log(`Telegram notifier initialized for ${strategyName}/${frameName}`); }, onSignal: (event, strategyName, frameName, backtest) => { console.log(`Signal event: ${event.action}`); } }}); Copy
import { addActionSchema } from "backtest-kit";// Define action handler classclass TelegramNotifier implements Partial<IAction> { constructor( private strategyName: StrategyName, private frameName: FrameName, private backtest: boolean ) {} signal(event: IStrategyTickResult): void { if (!this.backtest && event.action === 'opened') { telegram.send(`[${this.strategyName}/${this.frameName}] New signal`); } } dispose(): void { telegram.close(); }}// Register action schemaaddActionSchema({ actionName: "telegram-notifier", handler: TelegramNotifier, callbacks: { onInit: async (strategyName, frameName, backtest) => { console.log(`Telegram notifier initialized for ${strategyName}/${frameName}`); }, onSignal: (event, strategyName, frameName, backtest) => { console.log(`Signal event: ${event.action}`); } }});
Unique action identifier for registration
Optional
Optional lifecycle and event callbacks
Action handler constructor (instantiated per strategy-frame pair)
Optional developer note for documentation
Action schema registered via addActionSchema(). Defines event handler implementation and lifecycle callbacks for state management integration.
Actions provide a way to attach custom event handlers to strategies for:
Each action instance is created per strategy-frame pair and receives all events emitted during strategy execution. Multiple actions can be attached to a single strategy.
Example