canton_api_client/models/submit_and_wait_response.rs
1/*
2 * JSON Ledger API HTTP endpoints
3 *
4 * This specification version fixes the API inconsistencies where certain fields marked as required in the spec are in fact optional. If you use code generation tool based on this file, you might need to adjust the existing application code to handle those fields as optional. If you do not want to change your client code, continue using the OpenAPI specification for the latest Canton 3.4 patch release. MINIMUM_CANTON_VERSION=3.6.0
5 *
6 * The version of the OpenAPI document: 3.6.0-SNAPSHOT
7 *
8 * Generated by: https://openapi-generator.tech
9 */
10
11use crate::models;
12use serde::{Deserialize, Serialize};
13
14#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
15pub struct SubmitAndWaitResponse {
16 /// The id of the transaction that resulted from the submitted command. Must be a valid LedgerString (as described in ``value.proto``). Required
17 #[serde(rename = "updateId")]
18 pub update_id: String,
19 /// The details of the offset field are described in ``community/ledger-api/README.md``. Required
20 #[serde(rename = "completionOffset")]
21 pub completion_offset: i64,
22}
23
24impl SubmitAndWaitResponse {
25 pub fn new(update_id: String, completion_offset: i64) -> SubmitAndWaitResponse {
26 SubmitAndWaitResponse {
27 update_id,
28 completion_offset,
29 }
30 }
31}
32