canton_api_client/models/completion.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 from the previous Canton 3.4 patch release. MINIMUM_CANTON_VERSION=3.4.12
5 *
6 * The version of the OpenAPI document: 3.4.12-SNAPSHOT
7 *
8 * Generated by: https://openapi-generator.tech
9 */
10
11use crate::models;
12use serde::{Deserialize, Serialize};
13
14/// Completion : A completion represents the status of a submitted command on the ledger: it can be successful or failed.
15#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
16pub struct Completion {
17 #[serde(rename = "value")]
18 pub value: Box<models::Completion1>,
19}
20
21impl Completion {
22 /// A completion represents the status of a submitted command on the ledger: it can be successful or failed.
23 pub fn new(value: models::Completion1) -> Completion {
24 Completion {
25 value: Box::new(value),
26 }
27 }
28}
29