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

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Skipped		Jan 17, 2026 8:14pm

Greptile Summary

Added schema-based validation to block output path resolution to catch typos early. When a path is not found in runtime data, the resolver now checks if the path exists in the block's output schema - throwing an error for invalid paths (likely typos) while returning undefined for valid but missing paths (optional fields). The implementation includes a robust isPathInOutputSchema function that handles nested objects, arrays with numeric indices, and various schema formats (properties, items, etc.). Tests were updated to support the new schema validation and comprehensive test cases were added.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are well-tested with comprehensive test coverage, the logic is sound and handles edge cases properly, backwards compatibility is preserved, and the improvement helps catch user errors early
• No files require special attention

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant BlockResolver
    participant Schema as Output Schema
    participant Data as Runtime Data
    
    User->>BlockResolver: resolve("<block.field>")
    BlockResolver->>BlockResolver: Parse reference path
    BlockResolver->>Data: Look up block output
    
    alt Data contains path
        BlockResolver->>User: Return value
    else Data missing path
        BlockResolver->>BlockResolver: Check backwards compatibility
        alt Backwards compat matches
            BlockResolver->>User: Return adjusted value
        else No compat match
            BlockResolver->>Schema: Check if path exists in schema
            alt Path NOT in schema
                BlockResolver->>User: Throw error (typo detected)
            else Path in schema
                BlockResolver->>User: Return undefined (optional field)
            end
        end
    end