Name of the specific field (column) where the validation error occurs.
Specifies the exact field within the identified model that contains the validation error, or null for model-level errors that don't relate to a specific field. This corresponds to field names in primaryField, foreignFields, or plainFields arrays of the IModel interface.
Examples: "shopping_customer_id", "created_at", "name", null
When null, indicates model-level errors such as:
When string, indicates field-level errors such as:
This field information allows error-fixing systems to:
Detailed human-readable description of the validation error.
Provides comprehensive information about what validation rule was violated, why it's problematic, and often hints at how to resolve the issue. The message is designed to be informative enough for both automated error-fixing systems and human developers to understand and address the problem.
Message format typically includes:
This message information allows error-fixing systems to:
File path where the validation error occurs.
Specifies the exact schema file within the AutoBePrisma.IApplication.files array where this error was detected. This corresponds to the filename property of the IFile interface and enables targeted file-level error resolution.
Examples: "schema-01-articles.prisma", "schema-03-actors.prisma"
This path information allows error-fixing systems to:
Name of the model (database table) where the validation error occurs.
Specifies the exact model within the identified file that contains the validation error. This corresponds to the name property of the IModel interface and enables targeted model-level error resolution.
Examples: "shopping_customers", "bbs_articles", "mv_shopping_sale_last_snapshots"
When null, indicates file-level errors such as:
This model information allows error-fixing systems to:
Interface representing a specific validation error with precise location information.
This interface provides detailed information about individual validation errors, including exact location within the schema structure and comprehensive error descriptions. The location information enables error-fixing systems to pinpoint exactly where problems occur without manual search or guesswork.
Each error represents a specific violation of schema rules that must be resolved for successful validation.