/*
* SpatioAPI
*
* The REST API that owns every resource in your Spatio workspace: notes, sheets, slides, tasks, calendar events, mail, chat, files, and contacts. SpatioMCP wraps this API; Spatio Desktop reads from it. You can call it directly from your own code. All requests must be authenticated with a Personal Access Token (`Authorization: Bearer pat_...`) or an OAuth 2.1 access token, and use HTTPS. Official SDKs (MIT, generated from this spec on every release): - TypeScript: https://github.com/spatio-labs/spatio-ts (`npm install @spatio-labs/spatio-ts`) - Python: https://github.com/spatio-labs/spatio-py (`pip install spatio-sdk`) - Go: https://github.com/spatio-labs/spatio-go (`go get github.com/spatio-labs/spatio-go`) This specification is generated from the platform-service Go source on every push to `main`. The spec, not hand-written documentation, is the source of truth: server stubs and SDKs are generated from it, and any drift between the spec and the running service fails CI.
*
* The version of the OpenAPI document: v1
* Contact: hello@spatio.app
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
/// ListEventsData : Shape of `data` when returned by `listEvents`. Wrapped inside a CalendarOperationResult — clients should access this as `result.data` after checking `result.success`.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct ListEventsData {
/// `null` when there are no results (Go nil-slice serialization).
#[serde(rename = "events", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
pub events: Option<Option<Vec<models::SpatioEvent>>>,
#[serde(rename = "next_page_token", skip_serializing_if = "Option::is_none")]
pub next_page_token: Option<String>,
#[serde(rename = "total_results", skip_serializing_if = "Option::is_none")]
pub total_results: Option<i32>,
#[serde(rename = "updated_at")]
pub updated_at: chrono::DateTime<chrono::FixedOffset>,
}
impl ListEventsData {
/// Shape of `data` when returned by `listEvents`. Wrapped inside a CalendarOperationResult — clients should access this as `result.data` after checking `result.success`.
pub fn new(updated_at: chrono::DateTime<chrono::FixedOffset>) -> ListEventsData {
ListEventsData {
events: None,
next_page_token: None,
total_results: None,
updated_at,
}
}
}