Skip to content

Conversation

@kevinkim-ogp
Copy link
Contributor

@kevinkim-ogp kevinkim-ogp commented Nov 10, 2025

TL;DR

Added structured response capabilities to the PAIR action, allowing users to define multiple output fields with specific data types.

What changed?

  • Support two response formats: single field (existing) and multiple fields (new)
  • Schema validation for response fields with proper constraints:
    • Field names must use only letters, numbers, underscores, and hyphens
    • Category fields require comma-separated category values
    • At least one field is required when using multiple fields format
  • Utility functions to generate Zod schemas dynamically from field definitions

How to test?

  1. Use the PAIR action and select "Separate fields" as the response format
  2. Add multiple fields with different types:
    • Text fields for free-form text responses
    • Number fields for numeric values
    • Category fields with comma-separated options
  3. Run the action and verify that the response is structured according to your field definitions
  4. Try invalid configurations (empty field names, missing categories for category fields, field names that contain spaces or invalid characters) to test validation

Copy link
Contributor Author

kevinkim-ogp commented Nov 10, 2025

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@kevinkim-ogp kevinkim-ogp changed the title feat: Pair action multi field response [PAIR-4]: Pair action structured response Nov 10, 2025
@kevinkim-ogp kevinkim-ogp marked this pull request as ready for review November 10, 2025 08:49
@kevinkim-ogp kevinkim-ogp requested a review from a team as a code owner November 10, 2025 08:49
@kevinkim-ogp kevinkim-ogp changed the title [PAIR-4]: Pair action structured response [PAIR-2]: Pair action structured response Nov 12, 2025
@kevinkim-ogp kevinkim-ogp mentioned this pull request Nov 18, 2025
4 tasks
@kevinkim-ogp kevinkim-ogp marked this pull request as draft November 27, 2025 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants