@open-core/framework 1.0.1-beta.1 → 1.0.4-beta.1

package/dist/server/decorators/export.js

@@ -2,6 +2,44 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.Export = Export;
 const metadata_server_keys_1 = require("../system/metadata-server.keys");
+/**
+ * Export
+ * -----------------------------------------
+ * Declares a method as an externally accessible export
+ * within the FiveM environment.
+ *
+ * Methods decorated with `@Export()` are automatically
+ * registered by the framework and exposed as native
+ * FXServer exports, allowing other resources to call them
+ * using:
+ *
+ *   exports.resourceName.exportName(...)
+ *
+ * This decorator is typically used inside controller
+ * classes, where the framework’s module loader inspects
+ * metadata to register commands, events and exports
+ * consistently.
+ *
+ * @param name Optional name to expose. If omitted,
+ *             the method name is used.
+ *
+ * ```ts
+ * @Server.Controller()
+ * export class AccountController {
+ *   @Server.Export('getAccountById')
+ *   getAccount(id: string) {
+ *     return this.accountService.find(id)
+ *   }
+ * }
+ *
+ * // From another resource:
+ * // const result = exports['core-resource'].getAccountById('1234')
+ *```
+ * Internally, this decorator stores metadata used by
+ * the server bootstrap to automatically register the
+ * export through FXServer's `global.exports` API.
+ *
+ */
 function Export(name) {
     return (target, propertyKey) => {
         Reflect.defineMetadata(metadata_server_keys_1.METADATA_KEYS.EXPORT, { exportName: name || propertyKey }, target, propertyKey);

package/dist/server/decorators/guard.d.ts

@@ -1,5 +1,56 @@
 export interface GuardOptions {
+    /**
+     * Minimum rank required to execute the method.
+     * Permissions and Role/Ranks are defined by your Principal Controller
+     */
     rank?: number;
+    /**
+     * Permission required to execute the method.
+     * Permissions and Role/Ranks are defined by your Principal Controller
+     */
     permission?: string;
 }
+/**
+ * Guard
+ * ------------------------------------------------------------
+ * Declarative access-control decorator for controller methods.
+ *
+ * `@Guard()` protects a method by enforcing rank and/or
+ * permission requirements before executing it.
+ *
+ * Requirements are evaluated through the AccessControlService,
+ * which determines whether the player (first argument of the
+ * method) is authorized to perform the action.
+ *
+ * Usage of this decorator allows you to express authorization
+ * rules directly at the controller level, promoting a clean
+ * and explicit security model.
+ *
+ * @param options GuardOptions
+ *   - rank: minimum rank required to execute the method.
+ *   - permission: specific permission required.
+ *
+ * Notes:
+ * - The decorated method must receive a `Server.Player`
+ *   instance as its first argument.
+ * - When compiling improperly (e.g., benchmarks, stripped
+ *   decorators), the PropertyDescriptor may be missing.
+ *   In that case, only metadata is recorded and execution
+ *   fallback is disabled. This should *never* occur in a
+ *   production environment.
+ *
+ * ```ts
+ * export class FactionController {
+ *   @Server.Guard({ permission: 'factions.manage' })
+ *   async createFaction(player: Player, dto: CreateFactionDTO) {
+ *     return this.service.create(dto)
+ *   }
+ *
+ *   @Server.Guard({ rank: 3 })
+ *   async promoteMember(player: Player, memberID: string) {
+ *     return this.service.promote(player, memberID)
+ *   }
+ * }
+ * ```
+ */
 export declare function Guard(options: GuardOptions): (target: any, propertyKey: string, descriptor?: PropertyDescriptor) => PropertyDescriptor | undefined;

package/dist/server/decorators/guard.js

@@ -4,6 +4,49 @@ exports.Guard = Guard;
 const container_1 = require("../container");
 const services_1 = require("../services");
 const logger_1 = require("../../shared/logger");
+/**
+ * Guard
+ * ------------------------------------------------------------
+ * Declarative access-control decorator for controller methods.
+ *
+ * `@Guard()` protects a method by enforcing rank and/or
+ * permission requirements before executing it.
+ *
+ * Requirements are evaluated through the AccessControlService,
+ * which determines whether the player (first argument of the
+ * method) is authorized to perform the action.
+ *
+ * Usage of this decorator allows you to express authorization
+ * rules directly at the controller level, promoting a clean
+ * and explicit security model.
+ *
+ * @param options GuardOptions
+ *   - rank: minimum rank required to execute the method.
+ *   - permission: specific permission required.
+ *
+ * Notes:
+ * - The decorated method must receive a `Server.Player`
+ *   instance as its first argument.
+ * - When compiling improperly (e.g., benchmarks, stripped
+ *   decorators), the PropertyDescriptor may be missing.
+ *   In that case, only metadata is recorded and execution
+ *   fallback is disabled. This should *never* occur in a
+ *   production environment.
+ *
+ * ```ts
+ * export class FactionController {
+ *   @Server.Guard({ permission: 'factions.manage' })
+ *   async createFaction(player: Player, dto: CreateFactionDTO) {
+ *     return this.service.create(dto)
+ *   }
+ *
+ *   @Server.Guard({ rank: 3 })
+ *   async promoteMember(player: Player, memberID: string) {
+ *     return this.service.promote(player, memberID)
+ *   }
+ * }
+ * ```
+ */
 function Guard(options) {
     return function (target, propertyKey, descriptor) {
         var _a;

package/dist/server/decorators/index.d.ts

@@ -1,10 +1,10 @@
 export * from './bind';
 export * from './utils';
-export * from './command';
-export * from './coreEvent';
-export * from './netEvent';
+export { Command, CommandConfig } from './command';
+export * from './onFrameworkEvent';
+export * from './onNet';
 export * from './onTick';
-export * from './controller';
+export { Controller } from './controller';
 export * from './throttle';
 export * from './guard';
 export * from './requiresState';

package/dist/server/decorators/index.js

@@ -14,13 +14,16 @@ var __exportStar = (this && this.__exportStar) || function(m, exports) {
     for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
 };
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.Controller = exports.Command = void 0;
 __exportStar(require("./bind"), exports);
 __exportStar(require("./utils"), exports);
-__exportStar(require("./command"), exports);
-__exportStar(require("./coreEvent"), exports);
-__exportStar(require("./netEvent"), exports);
+var command_1 = require("./command");
+Object.defineProperty(exports, "Command", { enumerable: true, get: function () { return command_1.Command; } });
+__exportStar(require("./onFrameworkEvent"), exports);
+__exportStar(require("./onNet"), exports);
 __exportStar(require("./onTick"), exports);
-__exportStar(require("./controller"), exports);
+var controller_1 = require("./controller");
+Object.defineProperty(exports, "Controller", { enumerable: true, get: function () { return controller_1.Controller; } });
 __exportStar(require("./throttle"), exports);
 __exportStar(require("./guard"), exports);
 __exportStar(require("./requiresState"), exports);

package/dist/server/decorators/onFiveMEvent.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Listen to FiveM events server-side, check the list below
+ *
+ * https://docs.fivem.net/docs/scripting-reference/events/server-events/
+ */
+export declare function OnFiveMEvent(event: string): (target: any, propertyKey: string) => void;

package/dist/server/decorators/{coreEvent.js → onFiveMEvent.js}

@@ -1,9 +1,14 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.OnCoreEvent = OnCoreEvent;
+exports.OnFiveMEvent = OnFiveMEvent;
 const metadata_server_keys_1 = require("../system/metadata-server.keys");
-function OnCoreEvent(event) {
+/**
+ * Listen to FiveM events server-side, check the list below
+ *
+ * https://docs.fivem.net/docs/scripting-reference/events/server-events/
+ */
+function OnFiveMEvent(event) {
     return (target, propertyKey) => {
-        Reflect.defineMetadata(metadata_server_keys_1.METADATA_KEYS.CORE_EVENT, { event }, target, propertyKey);
+        Reflect.defineMetadata(metadata_server_keys_1.METADATA_KEYS.FIVEM_EVENT, { event }, target, propertyKey);
     };
 }

package/dist/server/decorators/onFrameworkEvent.d.ts

@@ -0,0 +1,22 @@
+import type { CoreEventMap } from '../types/core-events';
+/**
+ * Method decorator used to register a method as a listener for an internal OpenCore framework event.
+ *
+ * When the specified framework event is emitted, this method will be automatically triggered
+ * with the arguments provided by the event payload.
+ *
+ * @param event - The name of the core event to listen for (typed strictly to `CoreEventMap`).
+ *
+ *
+ * ```ts
+ * @Server.Controller()
+ * export class SystemController {
+ *
+ *   @OnFrameworkEvent('server:ready')
+ *   public onServerStart() {
+ *     console.log('OpenCore Framework is ready!')
+ *   }
+ * }
+ * ```
+ */
+export declare function OnFrameworkEvent<K extends keyof CoreEventMap>(event: K): (target: any, propertyKey: string) => void;

package/dist/server/decorators/onFrameworkEvent.js

@@ -0,0 +1,29 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.OnFrameworkEvent = OnFrameworkEvent;
+const metadata_server_keys_1 = require("../system/metadata-server.keys");
+/**
+ * Method decorator used to register a method as a listener for an internal OpenCore framework event.
+ *
+ * When the specified framework event is emitted, this method will be automatically triggered
+ * with the arguments provided by the event payload.
+ *
+ * @param event - The name of the core event to listen for (typed strictly to `CoreEventMap`).
+ *
+ *
+ * ```ts
+ * @Server.Controller()
+ * export class SystemController {
+ *
+ *   @OnFrameworkEvent('server:ready')
+ *   public onServerStart() {
+ *     console.log('OpenCore Framework is ready!')
+ *   }
+ * }
+ * ```
+ */
+function OnFrameworkEvent(event) {
+    return (target, propertyKey) => {
+        Reflect.defineMetadata(metadata_server_keys_1.METADATA_KEYS.CORE_EVENT, { event }, target, propertyKey);
+    };
+}

package/dist/server/decorators/onNet.d.ts

@@ -0,0 +1,58 @@
+import type { z } from 'zod';
+import type { Player } from '../entities/player';
+export interface NetEventOptions {
+    eventName: string;
+    schema?: z.ZodType;
+    paramTypes?: any;
+}
+type ServerNetHandler<TArgs extends any[] = any[]> = (player: Player, ...args: TArgs) => any;
+/**
+ * Registers a server-side network event handler.
+ *
+ * The decorated method is invoked when the client triggers
+ * `emitNet(eventName, ...)`.
+ *
+ * ## Player Injection
+ * The first argument of the handler **must be `Player`** and is automatically
+ * replaced with a `Server.Player` instance representing the client that
+ * fired the event. You do NOT need to read `source` manually.
+ *
+ * ## Auto-Validation
+ * Arguments after `Player` are automatically validated based on their TypeScript types:
+ * - `string` → `z.string()`
+ * - `number` → `z.number()`
+ * - `boolean` → `z.boolean()`
+ * - `any[]` → `z.array(z.any())` (array content not validated)
+ *
+ * ## Explicit Schema (Advanced)
+ * For stricter validation (ranges, formats, nested objects), provide a Zod schema:
+ *
+ * @example Auto-validation (simple)
+ * ```ts
+ * @OnNet("auth:login")
+ * handleLogin(player: Player, username: string, password: string) {
+ *   // username and password are validated as strings automatically
+ * }
+ * ```
+ *
+ * @example Explicit schema (strict validation)
+ * ```ts
+ * const transferSchema = z.object({
+ *   targetId: z.number().positive(),
+ *   amount: z.number().min(1).max(1000000),
+ * })
+ *
+ * @OnNet("bank:transfer", { schema: transferSchema })
+ * handleTransfer(player: Player, data: z.infer<typeof transferSchema>) {
+ *   // data.amount is guaranteed to be between 1 and 1,000,000
+ * }
+ * ```
+ *
+ * @param eventName - The network event name to listen for.
+ * @param options - Optional configuration object.
+ * @param options.schema - Zod schema for strict payload validation.
+ */
+export declare function OnNet<TArgs extends any[]>(eventName: string, options?: {
+    schema?: z.ZodType;
+}): <H extends ServerNetHandler<TArgs>>(target: any, propertyKey: string, descriptor: TypedPropertyDescriptor<H>) => void;
+export {};

package/dist/server/decorators/onNet.js

@@ -0,0 +1,57 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.OnNet = OnNet;
+const metadata_server_keys_1 = require("../system/metadata-server.keys");
+/**
+ * Registers a server-side network event handler.
+ *
+ * The decorated method is invoked when the client triggers
+ * `emitNet(eventName, ...)`.
+ *
+ * ## Player Injection
+ * The first argument of the handler **must be `Player`** and is automatically
+ * replaced with a `Server.Player` instance representing the client that
+ * fired the event. You do NOT need to read `source` manually.
+ *
+ * ## Auto-Validation
+ * Arguments after `Player` are automatically validated based on their TypeScript types:
+ * - `string` → `z.string()`
+ * - `number` → `z.number()`
+ * - `boolean` → `z.boolean()`
+ * - `any[]` → `z.array(z.any())` (array content not validated)
+ *
+ * ## Explicit Schema (Advanced)
+ * For stricter validation (ranges, formats, nested objects), provide a Zod schema:
+ *
+ * @example Auto-validation (simple)
+ * ```ts
+ * @OnNet("auth:login")
+ * handleLogin(player: Player, username: string, password: string) {
+ *   // username and password are validated as strings automatically
+ * }
+ * ```
+ *
+ * @example Explicit schema (strict validation)
+ * ```ts
+ * const transferSchema = z.object({
+ *   targetId: z.number().positive(),
+ *   amount: z.number().min(1).max(1000000),
+ * })
+ *
+ * @OnNet("bank:transfer", { schema: transferSchema })
+ * handleTransfer(player: Player, data: z.infer<typeof transferSchema>) {
+ *   // data.amount is guaranteed to be between 1 and 1,000,000
+ * }
+ * ```
+ *
+ * @param eventName - The network event name to listen for.
+ * @param options - Optional configuration object.
+ * @param options.schema - Zod schema for strict payload validation.
+ */
+function OnNet(eventName, options) {
+    return (target, propertyKey, descriptor) => {
+        const paramTypes = Reflect.getMetadata('design:paramtypes', target, propertyKey);
+        const metadata = { eventName, schema: options === null || options === void 0 ? void 0 : options.schema, paramTypes };
+        Reflect.defineMetadata(metadata_server_keys_1.METADATA_KEYS.NET_EVENT, metadata, target, propertyKey);
+    };
+}

package/dist/server/decorators/onTick.d.ts

@@ -1 +1,32 @@
+/**
+ * OnTick
+ * ------------------------------------------------------------
+ * Marks a method to be executed on every server tick.
+ *
+ * Methods decorated with `@OnTick()` are automatically
+ * registered by the framework's scheduler and invoked on each
+ * FXServer tick (~ every 0–10 ms depending on workload).
+ *
+ * This decorator should be used for lightweight recurring
+ * logic: status updates, background checks, cleanup tasks,
+ * or time-based processes relevant to gameplay.
+ *
+ * Heavy or blocking operations should be avoided inside tick
+ * handlers, as they directly impact global server performance.
+ *
+ * ```ts
+ * export class SyncController {
+ *   @OnTick()
+ *   updatePlayers() {
+ *     // Runs every tick
+ *     this.service.syncPositions()
+ *   }
+ * }
+ *
+ * ```
+ *
+ * Internally, the decorator only stores metadata. The
+ * server bootstrap scans for this metadata and binds the
+ * method to FiveM's tick cycle.
+ */
 export declare function OnTick(): (target: any, propertyKey: string) => void;

package/dist/server/decorators/onTick.js

@@ -2,6 +2,37 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.OnTick = OnTick;
 const metadata_server_keys_1 = require("../system/metadata-server.keys");
+/**
+ * OnTick
+ * ------------------------------------------------------------
+ * Marks a method to be executed on every server tick.
+ *
+ * Methods decorated with `@OnTick()` are automatically
+ * registered by the framework's scheduler and invoked on each
+ * FXServer tick (~ every 0–10 ms depending on workload).
+ *
+ * This decorator should be used for lightweight recurring
+ * logic: status updates, background checks, cleanup tasks,
+ * or time-based processes relevant to gameplay.
+ *
+ * Heavy or blocking operations should be avoided inside tick
+ * handlers, as they directly impact global server performance.
+ *
+ * ```ts
+ * export class SyncController {
+ *   @OnTick()
+ *   updatePlayers() {
+ *     // Runs every tick
+ *     this.service.syncPositions()
+ *   }
+ * }
+ *
+ * ```
+ *
+ * Internally, the decorator only stores metadata. The
+ * server bootstrap scans for this metadata and binds the
+ * method to FiveM's tick cycle.
+ */
 function OnTick() {
     return (target, propertyKey) => {
         Reflect.defineMetadata(metadata_server_keys_1.METADATA_KEYS.TICK, {}, target, propertyKey);

package/dist/server/decorators/public.d.ts

@@ -1,16 +1,27 @@
 /**
- * **Only works on NetEvents in Server-side**
+ * Marks a server-side NetEvent handler as publicly accessible.
  *
- * Marks an endpoint as publicly accessible (no authentication required).
- * Use only for login, register, or public info endpoints.
+ * This decorator disables authentication requirements for the
+ * decorated method. It should only be applied to endpoints used for:
+ * - Login
+ * - Registration
+ * - Public information retrieval
  *
- * @example
+ * ## Security Warning
+ * This decorator must be used with caution. Public endpoints must NOT
+ * modify sensitive game state unless necessary.
+ *
+ * ## Example
  * ```ts
  * class AuthServerController {
- *   @ Server.Public()
- *   @ Server.OnNet('auth:login')
- *   async login(player: Server.Player, credentials: AuthCredentials) { ... }
+ *   @Public()
+ *   @OnNet("auth:login")
+ *   async login(player: Server.Player, credentials: AuthCredentials) {
+ *     // no authentication required for this event
+ *   }
  * }
  * ```
- *  */
+ *
+ * @returns Method decorator that marks a handler as unauthenticated.
+ */
 export declare function Public(): (target: any, propertyKey: string, descriptor: PropertyDescriptor) => PropertyDescriptor;

package/dist/server/decorators/public.js

@@ -3,20 +3,31 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.Public = Public;
 const metadata_server_keys_1 = require("../system/metadata-server.keys");
 /**
- * **Only works on NetEvents in Server-side**
+ * Marks a server-side NetEvent handler as publicly accessible.
  *
- * Marks an endpoint as publicly accessible (no authentication required).
- * Use only for login, register, or public info endpoints.
+ * This decorator disables authentication requirements for the
+ * decorated method. It should only be applied to endpoints used for:
+ * - Login
+ * - Registration
+ * - Public information retrieval
  *
- * @example
+ * ## Security Warning
+ * This decorator must be used with caution. Public endpoints must NOT
+ * modify sensitive game state unless necessary.
+ *
+ * ## Example
  * ```ts
  * class AuthServerController {
- *   @ Server.Public()
- *   @ Server.OnNet('auth:login')
- *   async login(player: Server.Player, credentials: AuthCredentials) { ... }
+ *   @Public()
+ *   @OnNet("auth:login")
+ *   async login(player: Server.Player, credentials: AuthCredentials) {
+ *     // no authentication required for this event
+ *   }
  * }
  * ```
- *  */
+ *
+ * @returns Method decorator that marks a handler as unauthenticated.
+ */
 function Public() {
     return function (target, propertyKey, descriptor) {
         Reflect.defineMetadata(metadata_server_keys_1.METADATA_KEYS.PUBLIC, true, target, propertyKey);

package/dist/server/decorators/requiresState.d.ts

@@ -22,34 +22,35 @@ export interface StateRequirement {
     errorMessage?: string;
 }
 /**
- * **Game State Guard Decorator**
+ * Enforces gameplay state requirements before executing a method.
  *
- * A method decorator that enforces game logic constraints based on the player's dynamic states.
- * It intercepts the method call and validates the player's flags (e.g., 'dead', 'cuffed', 'driving')
- * before allowing the controller logic to execute.
+ * The decorator intercepts the method call and verifies whether
+ * the player satisfies required state flags (e.g. "dead", "cuffed",
+ * "on_duty_police").
  *
- * @remarks
- * - This decorator assumes the **first argument** of the decorated method is a `Server.Player` instance.
- * - It throws a `GAME_STATE_ERROR` (AppError) if requirements are not met, which should be caught by the global error handler.
+ * ## Whitelist (`has`)
+ * The player MUST have *all* required states. Missing any state blocks execution.
  *
- * @param req - The state requirements configuration (whitelist and/or blacklist).
+ * ## Blacklist (`missing`)
+ * The player MUST NOT have any of the forbidden states.
  *
- * @throws {Error} If the decorated method is called without a valid Player context (Server-side logic error).
- * @throws {AppError} If the player fails the state validation (Client-facing logic error).
+ * ## Error Handling
+ * - Throws a normal Error if the method is called without a valid Player.
+ * - Throws an `AppError(GAME_STATE_ERROR)` if validation fails.
  *
- * @example
+ * ## Example
  * ```ts
- * // Example 1: Action requires being alive (not dead) and not handcuffed
- * @RequiresState({ missing: ['dead', 'cuffed'] })
+ * @RequiresState({ missing: ["dead", "cuffed"] })
  * openInventory(player: Server.Player) { ... }
  *
- * // Example 2: Action requires being a police officer on duty
  * @RequiresState({
- * has: ['police_duty'],
- * missing: ['dead'],
- * errorMessage: 'You must be on duty to access the armory.'
+ *   has: ["police_duty"],
+ *   missing: ["dead"],
+ *   errorMessage: "You must be on duty to access the armory."
  * })
  * openArmory(player: Server.Player) { ... }
  * ```
+ *
+ * @param req - State validation configuration.
  */
 export declare function RequiresState(req: StateRequirement): (target: any, propertyKey: string, descriptor: PropertyDescriptor) => PropertyDescriptor;

package/dist/server/decorators/requiresState.js

@@ -3,35 +3,36 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.RequiresState = RequiresState;
 const utils_1 = require("../../utils");
 /**
- * **Game State Guard Decorator**
+ * Enforces gameplay state requirements before executing a method.
  *
- * A method decorator that enforces game logic constraints based on the player's dynamic states.
- * It intercepts the method call and validates the player's flags (e.g., 'dead', 'cuffed', 'driving')
- * before allowing the controller logic to execute.
+ * The decorator intercepts the method call and verifies whether
+ * the player satisfies required state flags (e.g. "dead", "cuffed",
+ * "on_duty_police").
  *
- * @remarks
- * - This decorator assumes the **first argument** of the decorated method is a `Server.Player` instance.
- * - It throws a `GAME_STATE_ERROR` (AppError) if requirements are not met, which should be caught by the global error handler.
+ * ## Whitelist (`has`)
+ * The player MUST have *all* required states. Missing any state blocks execution.
  *
- * @param req - The state requirements configuration (whitelist and/or blacklist).
+ * ## Blacklist (`missing`)
+ * The player MUST NOT have any of the forbidden states.
  *
- * @throws {Error} If the decorated method is called without a valid Player context (Server-side logic error).
- * @throws {AppError} If the player fails the state validation (Client-facing logic error).
+ * ## Error Handling
+ * - Throws a normal Error if the method is called without a valid Player.
+ * - Throws an `AppError(GAME_STATE_ERROR)` if validation fails.
  *
- * @example
+ * ## Example
  * ```ts
- * // Example 1: Action requires being alive (not dead) and not handcuffed
- * @RequiresState({ missing: ['dead', 'cuffed'] })
+ * @RequiresState({ missing: ["dead", "cuffed"] })
  * openInventory(player: Server.Player) { ... }
  *
- * // Example 2: Action requires being a police officer on duty
  * @RequiresState({
- * has: ['police_duty'],
- * missing: ['dead'],
- * errorMessage: 'You must be on duty to access the armory.'
+ *   has: ["police_duty"],
+ *   missing: ["dead"],
+ *   errorMessage: "You must be on duty to access the armory."
  * })
  * openArmory(player: Server.Player) { ... }
  * ```
+ *
+ * @param req - State validation configuration.
  */
 function RequiresState(req) {
     return function (target, propertyKey, descriptor) {