Property name (object key).
Must correspond to actual property names defined in target DTO schemas, API specifications, or business data models. Should use camelCase convention matching TypeScript interfaces.
API context: When used in request bodies for API operations, must exactly match the expected parameter names in the API specification.
Examples:
AI validation requirement: Ensure property names exist in the target schema and follow exact naming conventions used in API specifications.
Type discriminator for property assignments.
Always "propertyAssignment" to distinguish from other object construction mechanisms in the AST.
Property value expression.
Expression that evaluates to the property value. Type must match the expected type for this property in the target schema. Should represent realistic business data appropriate for the property's purpose.
API usage: When used in API operation parameters, must generate values compatible with the API specification requirements.
Common patterns:
AI type matching: Must generate expressions that produce values compatible with the target property's schema type and API constraints.
Property assignment for object literal construction.
Represents individual key-value pairs within object literals. Critical for building request bodies, configuration objects, and structured data that conforms to API schemas and business requirements, particularly for use in
IApiOperateStatement
operations.E2E testing importance: Each property assignment must align with DTO schema requirements to ensure valid API requests and realistic business data representation.
AI function calling requirement: Property names and value types must match target schema definitions exactly, especially when used for API operation parameters.