fix(copilot train): schema

[aadamgough]

Summary

Fix validation schmea

Type of Change

• Bug fix

Testing

How has this been tested? What should reviewers focus on?

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Nov 10, 2025 8:13pm

[greptile-apps]

Greptile Overview

Greptile Summary

Fixed validation schema mismatch in the copilot training API endpoint. The previous schema validated operations with fields (type, data, timestamp, metadata) that didn't match the actual data structure being sent from the training modal.

The corrected schema now properly validates:

• operation_type - The type of edit operation (add, edit, delete, insert_into_subflow, extract_from_subflow)
• block_id - The ID of the block being operated on
• params - Optional parameters for the operation

This aligns with the EditOperation interface defined in compute-edit-sequence.ts:3-18 and the actual data being sent from training-modal.tsx:130.

Confidence Score: 5/5

• This PR is safe to merge - it fixes a validation bug by correcting the schema to match actual data
• The change correctly aligns the Zod validation schema with the actual EditOperation interface and data being sent. The fix is straightforward, well-scoped, and resolves a validation mismatch that would have caused 400 errors
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
apps/sim/app/api/copilot/training/route.ts	5/5	Fixed validation schema to match actual operation data structure (operation_type, block_id, params)

Sequence Diagram

sequenceDiagram
participant Client as Training Modal
participant API as /api/copilot/training
participant Zod as Schema Validator
participant Indexer as Agent Indexer
Client->>API: POST training data
Note over Client,API: { title, prompt, input, output, operations }
API->>Zod: Validate request body
Note over Zod: TrainingDataSchema checks:<br/>- operations array<br/>- operation_type (string)<br/>- block_id (string)<br/>- params (optional)
alt Invalid Schema
Zod-->>API: Validation error
API-->>Client: 400 Bad Request
else Valid Schema
Zod-->>API: Validated data
API->>Indexer: POST /operations/add
Note over API,Indexer: Forwarded with x-api-key header
alt Indexer Success
Indexer-->>API: 200 OK
API-->>Client: Success response
else Indexer Error
Indexer-->>API: Error status
API-->>Client: Forward error status
end
end

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}