qeai-sdk 2.0.0

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

@@ -0,0 +1,126 @@
+/**
+ * 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 const PRODUCT_COMMANDS = {
+    // === Product core ===
+    /** Create a new product */
+    CREATE: 'product.create',
+    /** Retrieve all products with pagination support */
+    FIND_ALL: 'product.find-all',
+    /** Retrieve a specific product by ID */
+    FIND_ONE: 'product.find-one',
+    /** Update a product by ID */
+    UPDATE: 'product.update',
+    /** Soft delete a product (mark as inactive) */
+    DELETE: 'product.delete',
+    /** Validate a list of product IDs */
+    VALIDATE_PRODUCTS: 'product.validate-products',
+    // === ProductTag ===
+    /** Create relationship between product and tag */
+    TAG_CREATE: 'product-tag.create',
+    /** Retrieve all tags for a product */
+    TAG_FIND_BY_PRODUCT: 'product-tag.find-by-product-id',
+    /** Retrieve a specific tag for a product */
+    TAG_FIND_ONE: 'product-tag.find-one',
+    /** Replace all tags for a product */
+    TAG_REPLACE_BY_PRODUCT: 'product-tag.replace-by-product-id',
+    /** Remove relationship between product and tag */
+    TAG_REMOVE: 'product-tag.remove',
+    /** Remove all tag relationships for a product */
+    TAG_REMOVE_BY_PRODUCT: 'product-tag.remove-by-product-id',
+    // === ProductSize ===
+    /** Create a new product size */
+    SIZE_CREATE: 'product-size.create',
+    /** Retrieve all sizes for a product */
+    SIZE_FIND_BY_PRODUCT: 'product-size.find-by-product-id',
+    /** Retrieve specific size for a product by size ID */
+    SIZE_FIND_ONE: 'product-size.find-one',
+    /** Replace all sizes for a product */
+    SIZE_REPLACE_BY_PRODUCT: 'product-size.replace-by-product-id',
+    /** Update a size by ID */
+    SIZE_UPDATE: 'product-size.update',
+    /** Remove size by ID */
+    SIZE_REMOVE: 'product-size.remove',
+    /** Remove all sizes for a product */
+    SIZE_REMOVE_BY_PRODUCT: 'product-size.remove-by-product-id',
+    // === ProductSchedule ===
+    /** Create a new schedule for a product */
+    SCHEDULE_CREATE: 'product-schedule.create',
+    /** Retrieve all schedules for a product */
+    SCHEDULE_FIND_BY_PRODUCT: 'product-schedule.find-by-product-id',
+    /** Replace all schedules for a product */
+    SCHEDULE_REPLACE_BY_PRODUCT: 'product-schedule.replace-by-product-id',
+    /** Check if a product is available at a specific time */
+    SCHEDULE_IS_AVAILABLE_AT_TIME: 'product-schedule.is-available-at-time',
+    /** Retrieve specific product schedule by ID */
+    SCHEDULE_FIND_ONE: 'product-schedule.find-one',
+    /** Update a product schedule by ID */
+    SCHEDULE_UPDATE: 'product-schedule.update',
+    /** Remove a product schedule by ID */
+    SCHEDULE_REMOVE: 'product-schedule.remove',
+    /** Remove all schedules for a product */
+    SCHEDULE_REMOVE_BY_PRODUCT: 'product-schedule.remove-by-product-id',
+    // === ProductImage (preservando patrón aunque no se brindó el controlador) ===
+    /** Create a new image for a product */
+    IMAGE_CREATE: 'product-image.create',
+    /** Retrieve all images for a product */
+    IMAGE_FIND_BY_PRODUCT: 'product-image.find-by-product-id',
+    /** Retrieve specific image for a product by ID */
+    IMAGE_FIND_ONE: 'product-image.find-one',
+    /** Replace all images for a product */
+    IMAGE_REPLACE_BY_PRODUCT: 'product-image.replace-by-product-id',
+    /** Update a product image by ID */
+    IMAGE_UPDATE: 'product-image.update',
+    /** Remove a product image by ID */
+    IMAGE_REMOVE: 'product-image.remove',
+    /** Remove all images for a product */
+    IMAGE_REMOVE_BY_PRODUCT: 'product-image.remove-by-product-id',
+    // === ProductQuestion ===
+    /** Create a new question for a product */
+    QUESTION_CREATE: 'product-question.create',
+    /** Retrieve all questions for a product */
+    QUESTION_FIND_BY_PRODUCT: 'product-question.find-by-product-id',
+    /** Retrieve specific product question by ID */
+    QUESTION_FIND_ONE: 'product-question.find-one',
+    /** Replace all questions for a product */
+    QUESTION_REPLACE_BY_PRODUCT: 'product-question.replace-by-product-id',
+    /** Update a product question by ID */
+    QUESTION_UPDATE: 'product-question.update',
+    /** Remove a product question by ID */
+    QUESTION_REMOVE: 'product-question.remove',
+    /** Remove all product questions for a product */
+    QUESTION_REMOVE_BY_PRODUCT: 'product-question.remove-by-product-id',
+    // === ProductRecipe ===
+    /** Create a new recipe for a product */
+    RECIPE_CREATE: 'product-recipe.create',
+    /** Retrieve all recipes for a product */
+    RECIPE_FIND_BY_PRODUCT: 'product-recipe.find-by-product-id',
+    /** Retrieve specific product recipe by ID */
+    RECIPE_FIND_ONE: 'product-recipe.find-one',
+    /** Replace all recipes for a product */
+    RECIPE_REPLACE_BY_PRODUCT: 'product-recipe.replace-by-product-id',
+    /** Update a product recipe by ID */
+    RECIPE_UPDATE: 'product-recipe.update',
+    /** Remove a product recipe by ID */
+    RECIPE_REMOVE: 'product-recipe.remove',
+    /** Remove all recipes for a product */
+    RECIPE_REMOVE_BY_PRODUCT: 'product-recipe.remove-by-product-id',
+};

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

@@ -0,0 +1,32 @@
+/**
+ * Product-related event subjects.
+ *
+ * Centralized constant containing all event subject names
+ * that represent domain events emitted by the Product microservice.
+ *
+ * These event subjects are used in the distributed system (e.g., with NATS or other brokers)
+ * to notify other services or subsystems when significant actions occur on products or their
+ * submodules (such as creation of recipes, sizes, or tags).
+ *
+ * Usage examples:
+ *    - PRODUCT_EVENTS.CREATED: Emitted when a new product is created.
+ *    - PRODUCT_EVENTS.RECIPE_CREATED: Emitted when a new recipe is associated with a product.
+ *    - PRODUCT_EVENTS.TAG_CREATED: Emitted when a new tag is associated with a product.
+ *
+ * Keeping these values centralized ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ *
+ */
+export declare const PRODUCT_EVENTS: {
+    /** Emitted when a new product is created */
+    readonly CREATED: "product.created";
+    /** Emitted when a product is updated */
+    readonly UPDATED: "product.updated";
+    /** Emitted when a recipe is created for a product */
+    readonly RECIPE_CREATED: "product-recipe.created";
+    /** Emitted when a new size is created for a product */
+    readonly SIZE_CREATED: "product-size.created";
+    /** Emitted when a new tag is created for a product */
+    readonly TAG_CREATED: "product-tag.created";
+};

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

@@ -0,0 +1,32 @@
+/**
+ * Product-related event subjects.
+ *
+ * Centralized constant containing all event subject names
+ * that represent domain events emitted by the Product microservice.
+ *
+ * These event subjects are used in the distributed system (e.g., with NATS or other brokers)
+ * to notify other services or subsystems when significant actions occur on products or their
+ * submodules (such as creation of recipes, sizes, or tags).
+ *
+ * Usage examples:
+ *    - PRODUCT_EVENTS.CREATED: Emitted when a new product is created.
+ *    - PRODUCT_EVENTS.RECIPE_CREATED: Emitted when a new recipe is associated with a product.
+ *    - PRODUCT_EVENTS.TAG_CREATED: Emitted when a new tag is associated with a product.
+ *
+ * Keeping these values centralized ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ *
+ */
+export const PRODUCT_EVENTS = {
+    /** Emitted when a new product is created */
+    CREATED: "product.created",
+    /** Emitted when a product is updated */
+    UPDATED: "product.updated",
+    /** Emitted when a recipe is created for a product */
+    RECIPE_CREATED: "product-recipe.created",
+    /** Emitted when a new size is created for a product */
+    SIZE_CREATED: "product-size.created",
+    /** Emitted when a new tag is created for a product */
+    TAG_CREATED: "product-tag.created",
+};

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

@@ -0,0 +1,43 @@
+/**
+ * Question service command subjects.
+ *
+ * Centralized constant containing all subject/message keys handled by the Question microservice.
+ * Each key corresponds to a MessagePattern used for inter-service communication related to question management
+ * in product and menu modules.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the entity domain ('question').
+ *
+ * Usage examples:
+ *    - QUESTION_COMMANDS.CREATE: Subject for creating a question.
+ *    - QUESTION_COMMANDS.FIND_ALL: Subject for retrieving all questions.
+ *    - QUESTION_COMMANDS.FIND_ONE: Subject for fetching a specific question by ID.
+ *    - QUESTION_COMMANDS.SEARCH_BY_NAME: Subject for searching questions by name.
+ *    - QUESTION_COMMANDS.FIND_BY_TYPE: Subject for retrieving questions by their type.
+ *    - QUESTION_COMMANDS.FIND_BY_PRODUCT_ID: Subject for retrieving questions associated to a certain product.
+ *    - QUESTION_COMMANDS.UPDATE: Subject for updating a question.
+ *    - QUESTION_COMMANDS.REMOVE: Subject for soft-deleting a question.
+ *
+ * Centralizing these subjects ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ */
+export declare const QUESTION_COMMANDS: {
+    /** Create a new question */
+    readonly CREATE: "question.create";
+    /** Retrieve all questions with pagination */
+    readonly FIND_ALL: "question.find-all";
+    /** Retrieve a specific question by ID */
+    readonly FIND_ONE: "question.find-one";
+    /** Search questions by name */
+    readonly SEARCH_BY_NAME: "question.search-by-name";
+    /** Retrieve questions filtered by type */
+    readonly FIND_BY_TYPE: "question.find-by-type";
+    /** Retrieve questions associated with a specific product */
+    readonly FIND_BY_PRODUCT_ID: "question.find-by-product-id";
+    /** Update an existing question */
+    readonly UPDATE: "question.update";
+    /** Soft delete a question by ID */
+    readonly REMOVE: "question.remove";
+};

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

@@ -0,0 +1,43 @@
+/**
+ * Question service command subjects.
+ *
+ * Centralized constant containing all subject/message keys handled by the Question microservice.
+ * Each key corresponds to a MessagePattern used for inter-service communication related to question management
+ * in product and menu modules.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the entity domain ('question').
+ *
+ * Usage examples:
+ *    - QUESTION_COMMANDS.CREATE: Subject for creating a question.
+ *    - QUESTION_COMMANDS.FIND_ALL: Subject for retrieving all questions.
+ *    - QUESTION_COMMANDS.FIND_ONE: Subject for fetching a specific question by ID.
+ *    - QUESTION_COMMANDS.SEARCH_BY_NAME: Subject for searching questions by name.
+ *    - QUESTION_COMMANDS.FIND_BY_TYPE: Subject for retrieving questions by their type.
+ *    - QUESTION_COMMANDS.FIND_BY_PRODUCT_ID: Subject for retrieving questions associated to a certain product.
+ *    - QUESTION_COMMANDS.UPDATE: Subject for updating a question.
+ *    - QUESTION_COMMANDS.REMOVE: Subject for soft-deleting a question.
+ *
+ * Centralizing these subjects ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ */
+export const QUESTION_COMMANDS = {
+    /** Create a new question */
+    CREATE: 'question.create',
+    /** Retrieve all questions with pagination */
+    FIND_ALL: 'question.find-all',
+    /** Retrieve a specific question by ID */
+    FIND_ONE: 'question.find-one',
+    /** Search questions by name */
+    SEARCH_BY_NAME: 'question.search-by-name',
+    /** Retrieve questions filtered by type */
+    FIND_BY_TYPE: 'question.find-by-type',
+    /** Retrieve questions associated with a specific product */
+    FIND_BY_PRODUCT_ID: 'question.find-by-product-id',
+    /** Update an existing question */
+    UPDATE: 'question.update',
+    /** Soft delete a question by ID */
+    REMOVE: 'question.remove',
+};

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

@@ -0,0 +1,33 @@
+/**
+ * Restaurant service command subjects.
+ *
+ * Centralized constant containing all subject/message keys handled by the Restaurant microservice.
+ * Each key corresponds to a MessagePattern used for inter-service communication related to restaurant management.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the 'restaurant' entity domain.
+ *
+ * Usage examples:
+ *    - RESTAURANT_COMMANDS.CREATE: Subject for creating a restaurant.
+ *    - RESTAURANT_COMMANDS.FIND_ALL: Subject for retrieving all restaurants with pagination.
+ *    - RESTAURANT_COMMANDS.FIND_ONE: Subject for retrieving a restaurant by ID.
+ *    - RESTAURANT_COMMANDS.UPDATE: Subject for updating a restaurant.
+ *    - RESTAURANT_COMMANDS.DELETE: Subject for soft deleting a restaurant by ID.
+ *
+ * Centralizing these subjects ensures consistency, discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export declare const RESTAURANT_COMMANDS: {
+    /** Create a new restaurant */
+    readonly CREATE: "restaurant.create";
+    /** Retrieve all restaurants with pagination support */
+    readonly FIND_ALL: "restaurant.find-all";
+    /** Retrieve a specific restaurant by ID */
+    readonly FIND_ONE: "restaurant.find-one";
+    /** Update a restaurant by ID */
+    readonly UPDATE: "restaurant.update";
+    /** Soft delete a restaurant (mark as inactive) by ID */
+    readonly DELETE: "restaurant.delete";
+};

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

@@ -0,0 +1,33 @@
+/**
+ * Restaurant service command subjects.
+ *
+ * Centralized constant containing all subject/message keys handled by the Restaurant microservice.
+ * Each key corresponds to a MessagePattern used for inter-service communication related to restaurant management.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the 'restaurant' entity domain.
+ *
+ * Usage examples:
+ *    - RESTAURANT_COMMANDS.CREATE: Subject for creating a restaurant.
+ *    - RESTAURANT_COMMANDS.FIND_ALL: Subject for retrieving all restaurants with pagination.
+ *    - RESTAURANT_COMMANDS.FIND_ONE: Subject for retrieving a restaurant by ID.
+ *    - RESTAURANT_COMMANDS.UPDATE: Subject for updating a restaurant.
+ *    - RESTAURANT_COMMANDS.DELETE: Subject for soft deleting a restaurant by ID.
+ *
+ * Centralizing these subjects ensures consistency, discoverability, and maintainability across the codebase.
+ *
+ * @since 2.0.0
+ */
+export const RESTAURANT_COMMANDS = {
+    /** Create a new restaurant */
+    CREATE: 'restaurant.create',
+    /** Retrieve all restaurants with pagination support */
+    FIND_ALL: 'restaurant.find-all',
+    /** Retrieve a specific restaurant by ID */
+    FIND_ONE: 'restaurant.find-one',
+    /** Update a restaurant by ID */
+    UPDATE: 'restaurant.update',
+    /** Soft delete a restaurant (mark as inactive) by ID */
+    DELETE: 'restaurant.delete',
+};

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

@@ -0,0 +1,44 @@
+/**
+ * Tag service command subjects.
+ *
+ * Centralized constant containing all subject/message keys
+ * for commands between client(s) and the Tag microservice.
+ * Each key corresponds to a MessagePattern used for inter-service communication
+ * regarding tag management.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the entity domain ('tag').
+ *
+ * Usage examples:
+ *    - TAG_COMMANDS.CREATE: Subject for creating a tag.
+ *    - TAG_COMMANDS.FIND_ALL: Subject for listing all tags (with pagination).
+ *    - TAG_COMMANDS.SEARCH_BY_NAME: Subject for searching tags by name.
+ *    - TAG_COMMANDS.GET_MOST_USED: Subject for retrieving the most used tags.
+ *    - TAG_COMMANDS.FIND_BY_PRODUCT_ID: Subject for retrieving tags associated to a product.
+ *    - TAG_COMMANDS.FIND_ONE: Subject for fetching a tag by ID.
+ *    - TAG_COMMANDS.UPDATE: Subject for updating a tag.
+ *    - TAG_COMMANDS.REMOVE: Subject for soft deleting a tag by ID.
+ *
+ * Centralizing these keys ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ */
+export declare const TAG_COMMANDS: {
+    /** Create a new tag */
+    readonly CREATE: "tag.create";
+    /** Retrieve all tags with pagination support */
+    readonly FIND_ALL: "tag.find-all";
+    /** Search tags by name */
+    readonly SEARCH_BY_NAME: "tag.search-by-name";
+    /** Get most used tags */
+    readonly GET_MOST_USED: "tag.get-most-used";
+    /** Retrieve tags associated with a specific product */
+    readonly FIND_BY_PRODUCT_ID: "tag.find-by-product-id";
+    /** Retrieve a specific tag by ID */
+    readonly FIND_ONE: "tag.find-one";
+    /** Update an existing tag */
+    readonly UPDATE: "tag.update";
+    /** Soft delete a tag by ID */
+    readonly REMOVE: "tag.remove";
+};

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

@@ -0,0 +1,44 @@
+/**
+ * Tag service command subjects.
+ *
+ * Centralized constant containing all subject/message keys
+ * for commands between client(s) and the Tag microservice.
+ * Each key corresponds to a MessagePattern used for inter-service communication
+ * regarding tag management.
+ *
+ * Naming convention:
+ *  - Keys use SCREAMING_SNAKE_CASE.
+ *  - Subject values use kebab-case between dots, matching the entity domain ('tag').
+ *
+ * Usage examples:
+ *    - TAG_COMMANDS.CREATE: Subject for creating a tag.
+ *    - TAG_COMMANDS.FIND_ALL: Subject for listing all tags (with pagination).
+ *    - TAG_COMMANDS.SEARCH_BY_NAME: Subject for searching tags by name.
+ *    - TAG_COMMANDS.GET_MOST_USED: Subject for retrieving the most used tags.
+ *    - TAG_COMMANDS.FIND_BY_PRODUCT_ID: Subject for retrieving tags associated to a product.
+ *    - TAG_COMMANDS.FIND_ONE: Subject for fetching a tag by ID.
+ *    - TAG_COMMANDS.UPDATE: Subject for updating a tag.
+ *    - TAG_COMMANDS.REMOVE: Subject for soft deleting a tag by ID.
+ *
+ * Centralizing these keys ensures consistency, discoverability, and maintainability.
+ *
+ * @since 2.0.0
+ */
+export const TAG_COMMANDS = {
+    /** Create a new tag */
+    CREATE: 'tag.create',
+    /** Retrieve all tags with pagination support */
+    FIND_ALL: 'tag.find-all',
+    /** Search tags by name */
+    SEARCH_BY_NAME: 'tag.search-by-name',
+    /** Get most used tags */
+    GET_MOST_USED: 'tag.get-most-used',
+    /** Retrieve tags associated with a specific product */
+    FIND_BY_PRODUCT_ID: 'tag.find-by-product-id',
+    /** Retrieve a specific tag by ID */
+    FIND_ONE: 'tag.find-one',
+    /** Update an existing tag */
+    UPDATE: 'tag.update',
+    /** Soft delete a tag by ID */
+    REMOVE: 'tag.remove',
+};

package/dist/dtos/auth/index.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Authentication DTOs.
+ *
+ * This module exports DTOs used for authentication and user management
+ * in the Auth microservice.
+ *
+ * @since 2.0.0
+ */
+export * from './login-user.dto';
+export * from './register-user.dto';

package/dist/dtos/auth/index.js

@@ -0,0 +1,10 @@
+/**
+ * Authentication DTOs.
+ *
+ * This module exports DTOs used for authentication and user management
+ * in the Auth microservice.
+ *
+ * @since 2.0.0
+ */
+export * from './login-user.dto';
+export * from './register-user.dto';

package/dist/dtos/auth/login-user.dto.d.ts

@@ -0,0 +1,24 @@
+/**
+ * DTO for user login requests.
+ *
+ * Used by the Auth microservice to authenticate users.
+ * Validates email and password for authentication.
+ *
+ * @since 2.0.0
+ */
+export declare class LoginUserDto {
+    /**
+     * User's email address.
+     * Must be a valid email format.
+     *
+     * @example "john.doe@example.com"
+     */
+    email: string;
+    /**
+     * User's password.
+     * Must be at least 6 characters long.
+     *
+     * @example "SecurePass123!"
+     */
+    password: string;
+}

package/dist/dtos/auth/login-user.dto.js

@@ -0,0 +1,44 @@
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+var __metadata = (this && this.__metadata) || function (k, v) {
+    if (typeof Reflect === "object" && typeof Reflect.metadata === "function") return Reflect.metadata(k, v);
+};
+import { IsEmail, IsString, MinLength } from 'class-validator';
+/**
+ * DTO for user login requests.
+ *
+ * Used by the Auth microservice to authenticate users.
+ * Validates email and password for authentication.
+ *
+ * @since 2.0.0
+ */
+export class LoginUserDto {
+    /**
+     * User's email address.
+     * Must be a valid email format.
+     *
+     * @example "john.doe@example.com"
+     */
+    email;
+    /**
+     * User's password.
+     * Must be at least 6 characters long.
+     *
+     * @example "SecurePass123!"
+     */
+    password;
+}
+__decorate([
+    IsString(),
+    IsEmail(),
+    __metadata("design:type", String)
+], LoginUserDto.prototype, "email", void 0);
+__decorate([
+    IsString(),
+    MinLength(6),
+    __metadata("design:type", String)
+], LoginUserDto.prototype, "password", void 0);

package/dist/dtos/auth/register-user.dto.d.ts

@@ -0,0 +1,30 @@
+/**
+ * DTO for user registration requests.
+ *
+ * Used by the Auth microservice to handle new user registrations.
+ * Validates user input for creating new accounts with email and password.
+ *
+ * @since 2.0.0
+ */
+export declare class RegisterUserDto {
+    /**
+     * User's full name.
+     *
+     * @example "John Doe"
+     */
+    name: string;
+    /**
+     * User's email address.
+     * Must be a valid email format.
+     *
+     * @example "john.doe@example.com"
+     */
+    email: string;
+    /**
+     * User's password.
+     * Must be a strong password with minimum 8 characters.
+     *
+     * @example "SecurePass123!"
+     */
+    password: string;
+}

package/dist/dtos/auth/register-user.dto.js

@@ -0,0 +1,56 @@
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+var __metadata = (this && this.__metadata) || function (k, v) {
+    if (typeof Reflect === "object" && typeof Reflect.metadata === "function") return Reflect.metadata(k, v);
+};
+import { IsEmail, IsString, IsStrongPassword } from 'class-validator';
+/**
+ * DTO for user registration requests.
+ *
+ * Used by the Auth microservice to handle new user registrations.
+ * Validates user input for creating new accounts with email and password.
+ *
+ * @since 2.0.0
+ */
+export class RegisterUserDto {
+    /**
+     * User's full name.
+     *
+     * @example "John Doe"
+     */
+    name;
+    /**
+     * User's email address.
+     * Must be a valid email format.
+     *
+     * @example "john.doe@example.com"
+     */
+    email;
+    /**
+     * User's password.
+     * Must be a strong password with minimum 8 characters.
+     *
+     * @example "SecurePass123!"
+     */
+    password;
+}
+__decorate([
+    IsString(),
+    __metadata("design:type", String)
+], RegisterUserDto.prototype, "name", void 0);
+__decorate([
+    IsString(),
+    IsEmail(),
+    __metadata("design:type", String)
+], RegisterUserDto.prototype, "email", void 0);
+__decorate([
+    IsString(),
+    IsStrongPassword({
+        minLength: 8,
+    }),
+    __metadata("design:type", String)
+], RegisterUserDto.prototype, "password", void 0);

package/dist/dtos/categories/create-category.dto.d.ts

@@ -0,0 +1,38 @@
+/**
+ * DTO for creating a new category.
+ *
+ * Used by the Products microservice to create new product categories.
+ * Categories organize products and help customers navigate the menu.
+ *
+ * @since 2.0.0
+ */
+export declare class CreateCategoryDto {
+    /**
+     * Category name.
+     * Must not be empty.
+     *
+     * @example "Beverages"
+     */
+    name: string;
+    /**
+     * Optional category description.
+     *
+     * @example "All types of drinks and beverages"
+     */
+    description?: string;
+    /**
+     * Category status (active/inactive).
+     * Defaults to true if not provided.
+     *
+     * @example true
+     * @default true
+     */
+    status?: boolean;
+    /**
+     * User who created the category.
+     * Must be a valid MongoDB ObjectId.
+     *
+     * @example "507f1f77bcf86cd799439011"
+     */
+    createdBy: string;
+}