canton_api_client/models/
list_users_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#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
15pub struct ListUsersResponse {
16    /// A subset of users of the participant node that fit into this page. Can be empty if no more users  Optional: can be empty
17    #[serde(rename = "users", skip_serializing_if = "Option::is_none")]
18    pub users: Option<Vec<models::User>>,
19    /// Pagination token to retrieve the next page. Empty, if there are no further results.  Optional
20    #[serde(rename = "nextPageToken", skip_serializing_if = "Option::is_none")]
21    pub next_page_token: Option<String>,
22}
23
24impl ListUsersResponse {
25    pub fn new() -> ListUsersResponse {
26        ListUsersResponse {
27            users: None,
28            next_page_token: None,
29        }
30    }
31}
32
canton_api_client/models/list_users_response.rs

canton_api_client/models/
list_users_response.rs
