[76.4] JSON Plan File for Relational Constraints#97
Merged
kommundsen merged 1 commit intomainfrom Apr 9, 2026
Merged
Conversation
- GenerationPlan: deserialize plan files via System.Text.Json - PlanRunner: execute steps in order with binding resolution - RefResolver: evaluate $ref expressions with array expansion [*] - Binding validation: unrecognized keys and ambiguous scalar refs throw - 45 tests cover: deserialization, step ordering, ref resolution, type coercion, error cases
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implements the Plan module for JSON-based generation workflows. Enables users to define multi-step data generation plans via a
generation-plan.jsonfile with relational bindings between steps.Cycle 76.4 — JSON Plan File for Relational Constraints
Key features:
GenerationPlan: Deserialize plan files via System.Text.JsonPlanRunner: Execute steps in order with binding resolutionRefResolver: Evaluate$refexpressions with array expansion[*]Type of change
Checklist
dotnet test src/passes.editorconfigcode styleCloses #89
Part of #76