Number of items completed.
Tracks how many items have been successfully processed so far in the current operation. This value increments as each item is completed, providing real-time progress indication.
The ratio of completed to total gives the completion percentage:
progress = (completed / total) * 100
Schemas modified for relation compliance.
Contains ONLY the schemas that were actively modified to fix relation or structural issues, including both modified existing schemas and newly created schemas (extracted types, IInvert types).
An empty object {} indicates all relations were already properly structured.
Timestamp when the event was created.
ISO 8601 formatted date-time string indicating when this event was emitted by the system. This timestamp is crucial for event ordering, performance analysis, and debugging the agent workflow execution timeline.
Format: "YYYY-MM-DDTHH:mm:ss.sssZ" (e.g., "2024-01-15T14:30:45.123Z")
A unique identifier for the event.
Relation correction plan applied.
Outlines the specific relation fixes implemented including:
If relations were already correct, explicitly states that no fixes were required.
Relation violation findings from the review.
Documents all relation and structural issues discovered, categorized by type:
Each violation includes the affected schema, specific problem, and theoretical justification for the correction.
Original schemas submitted for relation review.
Contains the OpenAPI schemas that need relation and structural validation, including all DTOs with foreign keys, nested objects, or relation definitions requiring verification.
Current iteration number of the schema generation being reviewed.
Indicates which version of the schemas is undergoing relation review, helping track the iterative structural refinement process.
Detailed token usage metrics for the current operation.
Contains comprehensive token consumption data including total usage, input token breakdown with cache statistics, and output token categorization by generation type. This component-level tracking enables precise analysis of resource utilization for specific agent operations such as schema generation, test writing, or code implementation.
The token usage data helps identify optimization opportunities, monitor operational costs, and ensure efficient use of AI resources throughout the automated backend development process.
Total number of items to process.
Represents the complete count of operations, files, endpoints, or other entities that need to be processed in the current workflow step. This value is typically determined at the beginning of an operation and remains constant throughout the process.
Used together with the completed field to calculate progress percentage
and estimate time to completion.
Unique identifier for the event type.
A literal string that discriminates between different event types in the AutoBE system. This field enables TypeScript's discriminated union feature, allowing type-safe event handling through switch statements or conditional checks.
Examples: "analyzeWrite", "prismaSchema", "interfaceOperation", "testScenario"
Event fired during the relation and structure review phase of OpenAPI schema generation process.
This event represents the specialized relation validation activity of the Interface Schema Relation Review Agent, which focuses exclusively on DTO relations, foreign key transformations, and structural integrity. The agent ensures proper modeling of business domains while preventing circular references and enabling efficient code generation.
The Interface Schema Relation Review Agent performs targeted validation including:
Relation principles enforced:
Key characteristics of the relation review:
The review ensures that all DTOs accurately model the business domain with proper relations that enable code generation while preventing performance problems and circular dependencies.
Author
Kakasoo