canton_api_client/models/
js_active_contract.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 JsActiveContract {
16    #[serde(rename = "createdEvent")]
17    pub created_event: Box<models::CreatedEvent>,
18    /// A valid synchronizer id  Required
19    #[serde(rename = "synchronizerId")]
20    pub synchronizer_id: String,
21    /// Each corresponding assigned and unassigned event has the same reassignment_counter. This strictly increases with each unassign command for the same contract. Creation of the contract corresponds to reassignment_counter equals zero. This field will be the reassignment_counter of the latest observable activation event on this synchronizer, which is before the active_at_offset.  Required
22    #[serde(rename = "reassignmentCounter")]
23    pub reassignment_counter: i64,
24}
25
26impl JsActiveContract {
27    pub fn new(created_event: models::CreatedEvent, synchronizer_id: String, reassignment_counter: i64) -> JsActiveContract {
28        JsActiveContract {
29            created_event: Box::new(created_event),
30            synchronizer_id,
31            reassignment_counter,
32        }
33    }
34}
35
canton_api_client/models/js_active_contract.rs

canton_api_client/models/
js_active_contract.rs
