Conversation
jgpruitt
approved these changes
Apr 24, 2026
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
2 participants
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.
Summary
Allows YAML and Markdown imports to accept the
{start, end?}object form fortemporalfields. Previously this form was only accepted in JSON, which meant YAML and Markdown files produced byme memory exportcould not be re-imported without manual conversion.Changes
packages/cli/parsers/validation.ts: Removed the format restriction inparseTemporalInputso all import formats accept the object shape (which is the normalized API/export shape).packages/cli/parsers/import.test.ts: New tests covering YAML and Markdown imports of the object-formtemporalfield, including start-only.docs/formats.md: Updated the temporal input table and examples to reflect that all formats accept the object form, and removed the YAML-specific restriction note.Motivation
Export → import round-tripping should be lossless. YAML and Markdown exports emit
temporalas{start, end?}, so the import path needs to accept that shape.