[Deepbook SDK] Check user's locked balance before placing order.

[vivekascoder]

I think that it would be an improvement with errors if we check the user's locked balance first and make sure it's more than the amount he's placing an order for because otherwise you get error from balance module with an unreadable error message, unless you know know what that error code meant.

error: Dry run failed, could not automatically determine a budget: MoveAbort(MoveLocation { module: ModuleId { address: 0000000000000000000000000000000000000000000000000000000000000002, name: Identifier("balance") }, function: 7, instruction: 10, function_name: Some("split") }, 2) in command 0
 cause: {
  "effects": {
    "messageVersion": "v1",
    "status": {
      "status": "failure",
      "error": "MoveAbort(MoveLocation { module: ModuleId { address: 0000000000000000000000000000000000000000000000000000000000000002, name: Identifier(\"balance\") }, function: 7, instruction: 10, function_name: Some(\"split\") }, 2) in command 0"
    },
    "executedEpoch": "360",

what do you think? happy to work on it if you think it would be an improvement in the sdk.

[vivekascoder]

Another thing that could be an improvement is to take an optional TransactionalBlock here which will allow me to do something like depositing first and then adding limit order in the same transactional block.

I think each function should take an optional TransactionalBlock rather than returning a new one as it'll help to chain other things together i.e. making things composable.

[0xaslan]

Hey, thanks for the feedback! We will take care of things on the Move side, but feel free to create a PR on the SDK with the improvement you mentioned.