qeai-sdk 2.0.0

package/dist/constants/auth-commands.constant.d.ts

@@ -0,0 +1,25 @@
+/**
+ * Auth service command subjects.
+ *
+ * Centralized constant containing all subject/message keys
+ * for commands handled by the Auth microservice.
+ * Each key corresponds to a MessagePattern used in inter-service communication.
+ *
+ * Usage examples:
+ *    - AUTH_COMMANDS.REGISTER_USER: Subject for registering a new user.
+ *    - AUTH_COMMANDS.LOGIN_USER: Subject for user login.
+ *    - AUTH_COMMANDS.REFRESH_TOKEN: Subject for refreshing user JWT tokens.
+ *
+ * Keeping these values centralized ensures consistency,
+ * discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const AUTH_COMMANDS: {
+    /** Register a new user */
+    readonly REGISTER_USER: "auth.register-user";
+    /** Log in an existing user */
+    readonly LOGIN_USER: "auth.login-user";
+    /** Refresh the user's authentication token (JWT) */
+    readonly REFRESH_TOKEN: "auth.refresh-token";
+};

package/dist/constants/auth-commands.constant.js

@@ -0,0 +1,25 @@
+/**
+ * Auth service command subjects.
+ *
+ * Centralized constant containing all subject/message keys
+ * for commands handled by the Auth microservice.
+ * Each key corresponds to a MessagePattern used in inter-service communication.
+ *
+ * Usage examples:
+ *    - AUTH_COMMANDS.REGISTER_USER: Subject for registering a new user.
+ *    - AUTH_COMMANDS.LOGIN_USER: Subject for user login.
+ *    - AUTH_COMMANDS.REFRESH_TOKEN: Subject for refreshing user JWT tokens.
+ *
+ * Keeping these values centralized ensures consistency,
+ * discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export const AUTH_COMMANDS = {
+    /** Register a new user */
+    REGISTER_USER: 'auth.register-user',
+    /** Log in an existing user */
+    LOGIN_USER: 'auth.login-user',
+    /** Refresh the user's authentication token (JWT) */
+    REFRESH_TOKEN: 'auth.refresh-token',
+};

package/dist/constants/category-commands.constant.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Category service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Category microservice.
+ * Each key corresponds to a MessagePattern handled by the microservice.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the category domain.
+ *
+ * Usage examples:
+ *    - CATEGORY_COMMANDS.CREATE: Subject for creating a category.
+ *    - CATEGORY_COMMANDS.FIND_ALL: Subject for listing all categories (with pagination).
+ *    - CATEGORY_COMMANDS.FIND_ONE: Subject for retrieving a category by ID.
+ *    - CATEGORY_COMMANDS.UPDATE: Subject for updating a category.
+ *    - CATEGORY_COMMANDS.DELETE: Subject for soft deleting a category.
+ *
+ * Keeping these values centralized ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const CATEGORY_COMMANDS: {
+    /** Create a new category */
+    readonly CREATE: "category.create";
+    /** Retrieve all categories with pagination support */
+    readonly FIND_ALL: "category.find-all";
+    /** Retrieve a specific category by ID */
+    readonly FIND_ONE: "category.find-one";
+    /** Update a category by ID */
+    readonly UPDATE: "category.update";
+    /** Soft delete a category (mark as inactive) by ID */
+    readonly DELETE: "category.delete";
+};

package/dist/constants/category-commands.constant.js

@@ -0,0 +1,35 @@
+/**
+ * Category service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Category microservice.
+ * Each key corresponds to a MessagePattern handled by the microservice.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the category domain.
+ *
+ * Usage examples:
+ *    - CATEGORY_COMMANDS.CREATE: Subject for creating a category.
+ *    - CATEGORY_COMMANDS.FIND_ALL: Subject for listing all categories (with pagination).
+ *    - CATEGORY_COMMANDS.FIND_ONE: Subject for retrieving a category by ID.
+ *    - CATEGORY_COMMANDS.UPDATE: Subject for updating a category.
+ *    - CATEGORY_COMMANDS.DELETE: Subject for soft deleting a category.
+ *
+ * Keeping these values centralized ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export const CATEGORY_COMMANDS = {
+    /** Create a new category */
+    CREATE: 'category.create',
+    /** Retrieve all categories with pagination support */
+    FIND_ALL: 'category.find-all',
+    /** Retrieve a specific category by ID */
+    FIND_ONE: 'category.find-one',
+    /** Update a category by ID */
+    UPDATE: 'category.update',
+    /** Soft delete a category (mark as inactive) by ID */
+    DELETE: 'category.delete',
+};

package/dist/constants/chain-commands.constant.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Chain service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Chain microservice.
+ * Each key corresponds to a MessagePattern handled by the microservice.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the chain domain.
+ *
+ * Usage examples:
+ *    - CHAIN_COMMANDS.CREATE: Subject for creating a chain.
+ *    - CHAIN_COMMANDS.FIND_ALL: Subject for listing all chains (with pagination).
+ *    - CHAIN_COMMANDS.FIND_ONE: Subject for retrieving a chain by ID.
+ *    - CHAIN_COMMANDS.UPDATE: Subject for updating a chain.
+ *    - CHAIN_COMMANDS.DELETE: Subject for deleting a chain.
+ *
+ * Centralizing these values ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const CHAIN_COMMANDS: {
+    /** Create a new chain */
+    readonly CREATE: "chain.create";
+    /** Retrieve all chains with pagination support */
+    readonly FIND_ALL: "chain.find-all";
+    /** Retrieve a specific chain by ID */
+    readonly FIND_ONE: "chain.find-one";
+    /** Update a chain by ID */
+    readonly UPDATE: "chain.update";
+    /** Delete a chain by ID */
+    readonly DELETE: "chain.delete";
+};

package/dist/constants/chain-commands.constant.js

@@ -0,0 +1,35 @@
+/**
+ * Chain service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Chain microservice.
+ * Each key corresponds to a MessagePattern handled by the microservice.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the chain domain.
+ *
+ * Usage examples:
+ *    - CHAIN_COMMANDS.CREATE: Subject for creating a chain.
+ *    - CHAIN_COMMANDS.FIND_ALL: Subject for listing all chains (with pagination).
+ *    - CHAIN_COMMANDS.FIND_ONE: Subject for retrieving a chain by ID.
+ *    - CHAIN_COMMANDS.UPDATE: Subject for updating a chain.
+ *    - CHAIN_COMMANDS.DELETE: Subject for deleting a chain.
+ *
+ * Centralizing these values ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export const CHAIN_COMMANDS = {
+    /** Create a new chain */
+    CREATE: 'chain.create',
+    /** Retrieve all chains with pagination support */
+    FIND_ALL: 'chain.find-all',
+    /** Retrieve a specific chain by ID */
+    FIND_ONE: 'chain.find-one',
+    /** Update a chain by ID */
+    UPDATE: 'chain.update',
+    /** Delete a chain by ID */
+    DELETE: 'chain.delete',
+};

package/dist/constants/index.d.ts

@@ -0,0 +1,29 @@
+/**
+ * Centralized exports for all command and event constants.
+ *
+ * This barrel file exports all constants used for inter-service communication
+ * in the QeHay microservices architecture, including:
+ * - Command subjects (MessagePattern keys for requests)
+ * - Event subjects (domain events emitted by services)
+ *
+ * Usage examples:
+ *    - import { AUTH_COMMANDS, ORDER_COMMANDS } from 'looroh-sdk-qhay-interfaces';
+ *    - import { PRODUCT_EVENTS, PAYMENT_EVENTS } from 'looroh-sdk-qhay-interfaces';
+ *
+ * Centralizing exports here ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export * from './auth-commands.constant';
+export * from './category-commands.constant';
+export * from './chain-commands.constant';
+export * from './ingredient-commands.constant';
+export * from './order-commands.constant';
+export * from './payment-commands.constant';
+export * from './payment-events.constant';
+export * from './product-commands.constant';
+export * from './product-events.constant';
+export * from './question-commands.constant';
+export * from './restaurant-commands.constant';
+export * from './tag-commands.constant';

package/dist/constants/index.js

@@ -0,0 +1,39 @@
+/**
+ * Centralized exports for all command and event constants.
+ *
+ * This barrel file exports all constants used for inter-service communication
+ * in the QeHay microservices architecture, including:
+ * - Command subjects (MessagePattern keys for requests)
+ * - Event subjects (domain events emitted by services)
+ *
+ * Usage examples:
+ *    - import { AUTH_COMMANDS, ORDER_COMMANDS } from 'looroh-sdk-qhay-interfaces';
+ *    - import { PRODUCT_EVENTS, PAYMENT_EVENTS } from 'looroh-sdk-qhay-interfaces';
+ *
+ * Centralizing exports here ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+// Auth commands
+export * from './auth-commands.constant';
+// Category commands
+export * from './category-commands.constant';
+// Chain commands
+export * from './chain-commands.constant';
+// Ingredient commands
+export * from './ingredient-commands.constant';
+// Order commands
+export * from './order-commands.constant';
+// Payment commands and events
+export * from './payment-commands.constant';
+export * from './payment-events.constant';
+// Product commands and events
+export * from './product-commands.constant';
+export * from './product-events.constant';
+// Question commands
+export * from './question-commands.constant';
+// Restaurant commands
+export * from './restaurant-commands.constant';
+// Tag commands
+export * from './tag-commands.constant';

package/dist/constants/ingredient-commands.constant.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Ingredient service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Ingredient microservice.
+ * Each key corresponds to a MessagePattern handled by the microservice.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the ingredient domain.
+ *
+ * Usage examples:
+ *    - INGREDIENT_COMMANDS.CREATE: Subject for creating an ingredient.
+ *    - INGREDIENT_COMMANDS.FIND_ALL: Subject for listing all ingredients (with pagination).
+ *    - INGREDIENT_COMMANDS.FIND_ONE: Subject for retrieving an ingredient by ID.
+ *    - INGREDIENT_COMMANDS.UPDATE: Subject for updating an ingredient.
+ *    - INGREDIENT_COMMANDS.DELETE: Subject for soft deleting an ingredient.
+ *    - INGREDIENT_COMMANDS.SEARCH_BY_NAME: Subject for searching ingredients by name.
+ *
+ * Keeping these values centralized ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const INGREDIENT_COMMANDS: {
+    /** Create a new ingredient */
+    readonly CREATE: "ingredient.create";
+    /** Retrieve all ingredients with pagination support */
+    readonly FIND_ALL: "ingredient.find-all";
+    /** Retrieve a specific ingredient by ID */
+    readonly FIND_ONE: "ingredient.find-one";
+    /** Update an ingredient by ID */
+    readonly UPDATE: "ingredient.update";
+    /** Soft delete an ingredient (mark as inactive) by ID */
+    readonly DELETE: "ingredient.delete";
+    /** Search ingredients by name */
+    readonly SEARCH_BY_NAME: "ingredient.search-by-name";
+};

package/dist/constants/ingredient-commands.constant.js

@@ -0,0 +1,38 @@
+/**
+ * Ingredient service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Ingredient microservice.
+ * Each key corresponds to a MessagePattern handled by the microservice.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the ingredient domain.
+ *
+ * Usage examples:
+ *    - INGREDIENT_COMMANDS.CREATE: Subject for creating an ingredient.
+ *    - INGREDIENT_COMMANDS.FIND_ALL: Subject for listing all ingredients (with pagination).
+ *    - INGREDIENT_COMMANDS.FIND_ONE: Subject for retrieving an ingredient by ID.
+ *    - INGREDIENT_COMMANDS.UPDATE: Subject for updating an ingredient.
+ *    - INGREDIENT_COMMANDS.DELETE: Subject for soft deleting an ingredient.
+ *    - INGREDIENT_COMMANDS.SEARCH_BY_NAME: Subject for searching ingredients by name.
+ *
+ * Keeping these values centralized ensures consistency, discoverability,
+ * and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export const INGREDIENT_COMMANDS = {
+    /** Create a new ingredient */
+    CREATE: 'ingredient.create',
+    /** Retrieve all ingredients with pagination support */
+    FIND_ALL: 'ingredient.find-all',
+    /** Retrieve a specific ingredient by ID */
+    FIND_ONE: 'ingredient.find-one',
+    /** Update an ingredient by ID */
+    UPDATE: 'ingredient.update',
+    /** Soft delete an ingredient (mark as inactive) by ID */
+    DELETE: 'ingredient.delete',
+    /** Search ingredients by name */
+    SEARCH_BY_NAME: 'ingredient.search-by-name',
+};

package/dist/constants/order-commands.constant.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Order service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Order microservice.
+ * Each key corresponds to a subject (pattern) handled by the microservice controller.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the order domain.
+ *
+ * Usage examples:
+ *    - ORDER_COMMANDS.CREATE: Subject for creating an order.
+ *    - ORDER_COMMANDS.FIND_ALL: Subject for listing all orders.
+ *    - ORDER_COMMANDS.FIND_ONE: Subject for retrieving a single order by its id.
+ *    - ORDER_COMMANDS.FIND_ALL_BY_STATUS: Subject for retrieving all orders by status.
+ *    - ORDER_COMMANDS.CHANGE_STATUS: Subject for changing the status of an order.
+ *
+ * Maintaining these values in a centralized constant ensures consistency, discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const ORDER_COMMANDS: {
+    /** Create a new order */
+    readonly CREATE: "order.create";
+    /** Retrieve all orders with optional pagination/filtering */
+    readonly FIND_ALL: "order.find-all";
+    /** Retrieve a single order by its unique identifier */
+    readonly FIND_ONE: "order.find-one";
+    /** Retrieve all orders by status */
+    readonly FIND_ALL_BY_STATUS: "order.find-all";
+    /** Change the status of a specific order */
+    readonly CHANGE_STATUS: "order.change-status";
+};

package/dist/constants/order-commands.constant.js

@@ -0,0 +1,34 @@
+/**
+ * Order service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Order microservice.
+ * Each key corresponds to a subject (pattern) handled by the microservice controller.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the order domain.
+ *
+ * Usage examples:
+ *    - ORDER_COMMANDS.CREATE: Subject for creating an order.
+ *    - ORDER_COMMANDS.FIND_ALL: Subject for listing all orders.
+ *    - ORDER_COMMANDS.FIND_ONE: Subject for retrieving a single order by its id.
+ *    - ORDER_COMMANDS.FIND_ALL_BY_STATUS: Subject for retrieving all orders by status.
+ *    - ORDER_COMMANDS.CHANGE_STATUS: Subject for changing the status of an order.
+ *
+ * Maintaining these values in a centralized constant ensures consistency, discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export const ORDER_COMMANDS = {
+    /** Create a new order */
+    CREATE: 'order.create',
+    /** Retrieve all orders with optional pagination/filtering */
+    FIND_ALL: 'order.find-all',
+    /** Retrieve a single order by its unique identifier */
+    FIND_ONE: 'order.find-one',
+    /** Retrieve all orders by status */
+    FIND_ALL_BY_STATUS: 'order.find-all', // The subject is reused with status filter
+    /** Change the status of a specific order */
+    CHANGE_STATUS: 'order.change-status',
+};

package/dist/constants/payment-commands.constant.d.ts

@@ -0,0 +1,31 @@
+/**
+ * Payment service command subjects.
+ *
+ * Centralized constant containing all subject/message keys
+ * handled by the Payment microservice. Each key corresponds to a subject (pattern)
+ * used in inter-service or client-to-microservice communication.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the payment domain.
+ *
+ * Usage examples:
+ *    - PAYMENT_COMMANDS.CREATE_PAYMENT_SESSION: Subject for creating a payment session.
+ *    - PAYMENT_COMMANDS.PAYMENT_SUCCESS: Subject for handling payment success event.
+ *    - PAYMENT_COMMANDS.PAYMENT_CANCEL: Subject for handling payment cancel event.
+ *    - PAYMENT_COMMANDS.PAYMENT_STRIPE_WEBHOOK: Subject for handling Stripe webhook events.
+ *
+ * Maintaining these values in a centralized constant ensures consistency, discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const PAYMENT_COMMANDS: {
+    /** Create a new payment session */
+    readonly PAYMENT_CREATE_SESSION: "payment.create-session";
+    /** Handle successful payment callback */
+    readonly PAYMENT_SUCCESS: "payment.success";
+    /** Handle canceled payment callback */
+    readonly PAYMENT_CANCEL: "payment.cancel";
+    /** Handle webhook events from Stripe or similar providers */
+    readonly PAYMENT_STRIPE_WEBHOOK: "payment.stripe-webhook";
+};

package/dist/constants/payment-commands.constant.js

@@ -0,0 +1,31 @@
+/**
+ * Payment service command subjects.
+ *
+ * Centralized constant containing all subject/message keys
+ * handled by the Payment microservice. Each key corresponds to a subject (pattern)
+ * used in inter-service or client-to-microservice communication.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the payment domain.
+ *
+ * Usage examples:
+ *    - PAYMENT_COMMANDS.CREATE_PAYMENT_SESSION: Subject for creating a payment session.
+ *    - PAYMENT_COMMANDS.PAYMENT_SUCCESS: Subject for handling payment success event.
+ *    - PAYMENT_COMMANDS.PAYMENT_CANCEL: Subject for handling payment cancel event.
+ *    - PAYMENT_COMMANDS.PAYMENT_STRIPE_WEBHOOK: Subject for handling Stripe webhook events.
+ *
+ * Maintaining these values in a centralized constant ensures consistency, discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export const PAYMENT_COMMANDS = {
+    /** Create a new payment session */
+    PAYMENT_CREATE_SESSION: 'payment.create-session',
+    /** Handle successful payment callback */
+    PAYMENT_SUCCESS: 'payment.success',
+    /** Handle canceled payment callback */
+    PAYMENT_CANCEL: 'payment.cancel',
+    /** Handle webhook events from Stripe or similar providers */
+    PAYMENT_STRIPE_WEBHOOK: 'payment.stripe-webhook',
+};

package/dist/constants/payment-events.constant.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Payment-related event subjects.
+ *
+ * Centralized constant containing all event subject names
+ * that represent domain events emitted by the Payment microservice.
+ *
+ * Usage example:
+ *    - PAYMENT_EVENTS.SUCCEEDED: Emitted when a payment is successfully processed.
+ *
+ * Keeping these values centralized ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ */
+export declare const PAYMENT_EVENTS: {
+    /** Emitted when a payment is successfully processed */
+    readonly SUCCEEDED: "payment.succeeded";
+};

package/dist/constants/payment-events.constant.js

@@ -0,0 +1,17 @@
+/**
+ * Payment-related event subjects.
+ *
+ * Centralized constant containing all event subject names
+ * that represent domain events emitted by the Payment microservice.
+ *
+ * Usage example:
+ *    - PAYMENT_EVENTS.SUCCEEDED: Emitted when a payment is successfully processed.
+ *
+ * Keeping these values centralized ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ */
+export const PAYMENT_EVENTS = {
+    /** Emitted when a payment is successfully processed */
+    SUCCEEDED: "payment.succeeded",
+};

package/dist/constants/product-commands.constant.d.ts

@@ -0,0 +1,119 @@
+/**
+ * Product service command subjects.
+ *
+ * Centralized constant with all subject/message keys
+ * for commands between client(s) and the Product microservice.
+ * This includes core product commands and those for product submodules
+ * such as tag, size, schedule, image, question, and recipe management.
+ *
+ * Each key corresponds to a MessagePattern handled somewhere in the Product service.
+ *
+ * Usage examples:
+ *    - PRODUCT_COMMANDS.CREATE: Subject for creating a product.
+ *    - PRODUCT_COMMANDS.TAG_CREATE: Subject for creating a product-tag relationship.
+ *    - PRODUCT_COMMANDS.SIZE_FIND_ALL: Subject for listing all sizes for a product.
+ *    - PRODUCT_COMMANDS.SCHEDULE_REMOVE_BY_PRODUCT: Subject for deleting all schedules for a product.
+ *    - etc.
+ *
+ * Keeping these values centralized ensures consistency, discoverability and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const PRODUCT_COMMANDS: {
+    /** Create a new product */
+    readonly CREATE: "product.create";
+    /** Retrieve all products with pagination support */
+    readonly FIND_ALL: "product.find-all";
+    /** Retrieve a specific product by ID */
+    readonly FIND_ONE: "product.find-one";
+    /** Update a product by ID */
+    readonly UPDATE: "product.update";
+    /** Soft delete a product (mark as inactive) */
+    readonly DELETE: "product.delete";
+    /** Validate a list of product IDs */
+    readonly VALIDATE_PRODUCTS: "product.validate-products";
+    /** Create relationship between product and tag */
+    readonly TAG_CREATE: "product-tag.create";
+    /** Retrieve all tags for a product */
+    readonly TAG_FIND_BY_PRODUCT: "product-tag.find-by-product-id";
+    /** Retrieve a specific tag for a product */
+    readonly TAG_FIND_ONE: "product-tag.find-one";
+    /** Replace all tags for a product */
+    readonly TAG_REPLACE_BY_PRODUCT: "product-tag.replace-by-product-id";
+    /** Remove relationship between product and tag */
+    readonly TAG_REMOVE: "product-tag.remove";
+    /** Remove all tag relationships for a product */
+    readonly TAG_REMOVE_BY_PRODUCT: "product-tag.remove-by-product-id";
+    /** Create a new product size */
+    readonly SIZE_CREATE: "product-size.create";
+    /** Retrieve all sizes for a product */
+    readonly SIZE_FIND_BY_PRODUCT: "product-size.find-by-product-id";
+    /** Retrieve specific size for a product by size ID */
+    readonly SIZE_FIND_ONE: "product-size.find-one";
+    /** Replace all sizes for a product */
+    readonly SIZE_REPLACE_BY_PRODUCT: "product-size.replace-by-product-id";
+    /** Update a size by ID */
+    readonly SIZE_UPDATE: "product-size.update";
+    /** Remove size by ID */
+    readonly SIZE_REMOVE: "product-size.remove";
+    /** Remove all sizes for a product */
+    readonly SIZE_REMOVE_BY_PRODUCT: "product-size.remove-by-product-id";
+    /** Create a new schedule for a product */
+    readonly SCHEDULE_CREATE: "product-schedule.create";
+    /** Retrieve all schedules for a product */
+    readonly SCHEDULE_FIND_BY_PRODUCT: "product-schedule.find-by-product-id";
+    /** Replace all schedules for a product */
+    readonly SCHEDULE_REPLACE_BY_PRODUCT: "product-schedule.replace-by-product-id";
+    /** Check if a product is available at a specific time */
+    readonly SCHEDULE_IS_AVAILABLE_AT_TIME: "product-schedule.is-available-at-time";
+    /** Retrieve specific product schedule by ID */
+    readonly SCHEDULE_FIND_ONE: "product-schedule.find-one";
+    /** Update a product schedule by ID */
+    readonly SCHEDULE_UPDATE: "product-schedule.update";
+    /** Remove a product schedule by ID */
+    readonly SCHEDULE_REMOVE: "product-schedule.remove";
+    /** Remove all schedules for a product */
+    readonly SCHEDULE_REMOVE_BY_PRODUCT: "product-schedule.remove-by-product-id";
+    /** Create a new image for a product */
+    readonly IMAGE_CREATE: "product-image.create";
+    /** Retrieve all images for a product */
+    readonly IMAGE_FIND_BY_PRODUCT: "product-image.find-by-product-id";
+    /** Retrieve specific image for a product by ID */
+    readonly IMAGE_FIND_ONE: "product-image.find-one";
+    /** Replace all images for a product */
+    readonly IMAGE_REPLACE_BY_PRODUCT: "product-image.replace-by-product-id";
+    /** Update a product image by ID */
+    readonly IMAGE_UPDATE: "product-image.update";
+    /** Remove a product image by ID */
+    readonly IMAGE_REMOVE: "product-image.remove";
+    /** Remove all images for a product */
+    readonly IMAGE_REMOVE_BY_PRODUCT: "product-image.remove-by-product-id";
+    /** Create a new question for a product */
+    readonly QUESTION_CREATE: "product-question.create";
+    /** Retrieve all questions for a product */
+    readonly QUESTION_FIND_BY_PRODUCT: "product-question.find-by-product-id";
+    /** Retrieve specific product question by ID */
+    readonly QUESTION_FIND_ONE: "product-question.find-one";
+    /** Replace all questions for a product */
+    readonly QUESTION_REPLACE_BY_PRODUCT: "product-question.replace-by-product-id";
+    /** Update a product question by ID */
+    readonly QUESTION_UPDATE: "product-question.update";
+    /** Remove a product question by ID */
+    readonly QUESTION_REMOVE: "product-question.remove";
+    /** Remove all product questions for a product */
+    readonly QUESTION_REMOVE_BY_PRODUCT: "product-question.remove-by-product-id";
+    /** Create a new recipe for a product */
+    readonly RECIPE_CREATE: "product-recipe.create";
+    /** Retrieve all recipes for a product */
+    readonly RECIPE_FIND_BY_PRODUCT: "product-recipe.find-by-product-id";
+    /** Retrieve specific product recipe by ID */
+    readonly RECIPE_FIND_ONE: "product-recipe.find-one";
+    /** Replace all recipes for a product */
+    readonly RECIPE_REPLACE_BY_PRODUCT: "product-recipe.replace-by-product-id";
+    /** Update a product recipe by ID */
+    readonly RECIPE_UPDATE: "product-recipe.update";
+    /** Remove a product recipe by ID */
+    readonly RECIPE_REMOVE: "product-recipe.remove";
+    /** Remove all recipes for a product */
+    readonly RECIPE_REMOVE_BY_PRODUCT: "product-recipe.remove-by-product-id";
+};