canton_api_client/models/js_get_update_trees_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 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/// JsGetUpdateTreesResponse : Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
15#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
16pub struct JsGetUpdateTreesResponse {
17 #[serde(rename = "update", skip_serializing_if = "Option::is_none")]
18 pub update: Option<Box<models::Update1>>,
19}
20
21impl JsGetUpdateTreesResponse {
22 /// Provided for backwards compatibility, it will be removed in the Canton version 3.5.0.
23 pub fn new() -> JsGetUpdateTreesResponse {
24 JsGetUpdateTreesResponse {
25 update: None,
26 }
27 }
28}
29