[Docs] Improve escrow creation example to have ExecuteAfter date #820
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.
The existing example of an escrowCreation transaction in the docs includes
allowCancelAfter
but not anallowExecuteAfter
field (and also no condition field)—this is the exact arrangement that can cause "false escrows" like the ones Ripple mistakenly made with the first set of the 55B escrows—they can be finished by anyone at any time before the cancellation.This PR edits the example test fixture to add an
allowExecuteAfter
field. This provides a better example, but should be functionally identical as a test fixture because the statedallowCancelAfter
date is still in the past.