Repository navigation
Conversation
Inside a role's archive.md, spec_for now prefers the matching spec whose in= names the record's section, so a closed entry archived in full can be checked against a Closed spec instead of the Open one. Elsewhere it takes the first matching spec, as before.
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.
Inside a role's
archive.md, a record is now checked against the matching spec whoseinnames the section it sits under. That lets a project archive closed delta entries in full against a Closed spec, instead of the Open spec with its requiredWaits on. Outside an archive nothing changes.Templates.test_an_archive_uses_the_spec_for_its_sectionfails without the change (D-009 has no 'Waits on' field) and passes with it. The full suite passes.checkoutput is byte-identical on a real migrating set, and the examples stay clean."1.0"stays valid.