Block Explorer API - batch transaction errors #7245
Labels
api
block-explorer
discussion
fe-request
A list of reasonably high value API change requests from front end
feature
new feature to be developed
Milestone
Feature Overview
In order to usefully render the success or failure of a batch order
We will need improve on the simply returning the error field
So that individual transactions in the batch can be marked as successful or failed
and the success of the batch as a whole can be represented
Tasks
Acceptance Criteria
Test Scenarios (non-exhaustive)
GIVEN a batch transaction with 2 cancellations
WHEN the first cancellation is for an order that does not exist
THEN the cancellation within the command object has an error field and that error field contains the error unable to find the order in the market
GIVEN a batch transaction with 2 amendments
WHEN the first amendment is for an order that is filled
THEN the amendment within the command object has an error field and that error field contains the error
GIVEN a batch transaction with 2 submissions
WHEN the first order is for a market that does not exist
THEN the order within the command object has an error field and that error field contains the error
Additional Details (optional)
tldr this is an API addition, not a TX change, with the goal of ensuring that bost algorthmic/API traders AND front end developers can ascertain the status of each component of a batch in order to update state, take further actions, and display information about the status to users.
It is important, particularly for API traders, that the data is structued and that there can be no "surprises".
See also #7246
The text was updated successfully, but these errors were encountered: