/*
* JSON Ledger API HTTP endpoints
*
* 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
*
* The version of the OpenAPI document: 3.6.0-SNAPSHOT
*
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct JsGetActiveContractsResponse {
/// The workflow ID used in command submission which corresponds to the contract_entry. Only set if the ``workflow_id`` for the command was set. Must be a valid LedgerString (as described in ``value.proto``). Optional
#[serde(rename = "workflowId", skip_serializing_if = "Option::is_none")]
pub workflow_id: Option<String>,
#[serde(rename = "contractEntry", skip_serializing_if = "Option::is_none")]
pub contract_entry: Option<Box<models::JsContractEntry>>,
/// Opaque representation of a continuation token which can be used in the request to bypass the already processed part of the active contracts snapshot. Only populated for the streaming ``GetActiveContracts`` rpc call. Optional: can be empty
#[serde(rename = "streamContinuationToken", skip_serializing_if = "Option::is_none")]
pub stream_continuation_token: Option<String>,
}
impl JsGetActiveContractsResponse {
pub fn new() -> JsGetActiveContractsResponse {
JsGetActiveContractsResponse {
workflow_id: None,
contract_entry: None,
stream_continuation_token: None,
}
}
}