Explicitly record full document completion in PFFTT#124
Merged
Conversation
Member
Author
|
Further implements |
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
1 participant
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.
Record a new
Finishstate to complement theStartline, closing the run of a document. We had a Begin/Done pair around the entry procedure (if there was one) but nothing actually pairing with the start of the Technique.This came up when we wanted to embellish the interactive trace with a new visual convention: double arrows '⇒' and '⇐' are used to mark the entry and exit from a Technique document as a whole (in contrast to the single arrows which mark movement within the document) and we realized we didn't have a compliment for
Start.Add support for
file://URLs as external invocation targets. That was always implied but got missed along the way. Fixed.