Run a YAML spec over the source - #60
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Layer 1 of a draft. A spec is a small YAML file of selectors over the pandoc AST that says which blocks are questions, parts and solutions, with strip patterns, ignore rules and a layout. The four filters stay exactly as they are and are what the layout field names: a spec with
layout: PartsSepSolapplies that filter's logic to the blocks the selectors picked out. The worked example in the agent spec shows the shape:in2lambda spec run SPECfills the draft's fields with provenance, records the spec's hash in the draft, and returns coverage: which blocks are in no field and not ignored. Done when each saved spec plus its source in the test data produces its expected draft, so a new pair dropped in the test data is a new test with no code, and a spec that names an unknown layout or selector is refused with the line.Workbench ticket t26.