canton_api_client/models/party_management_feature.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 PartyManagementFeature {
16 /// The maximum number of parties the server can return in a single response (page). Required
17 #[serde(rename = "maxPartiesPageSize")]
18 pub max_parties_page_size: i32,
19}
20
21impl PartyManagementFeature {
22 pub fn new(max_parties_page_size: i32) -> PartyManagementFeature {
23 PartyManagementFeature {
24 max_parties_page_size,
25 }
26 }
27}
28