History transitions are now indicated using the history keyword
#1247
Conversation
This file contains 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
the different types would actually make a difference in behavior.
unspecified transitions types
lhstrh
approved these changes
Jun 24, 2022
lhstrh
changed the title
continue to history
lhstrh
changed the title
continue to historyhistory keyword
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.
Changes keyword for history transitions from
continuetohistory.The documentation is updated by website PR #87.
Update of the syntax highlighting for VSCode in vscode PR #62.
Also adds warning if the user does not specify a transition type but the types would actually have different effects on the target mode.
Closes #1220