bmlt-server-semantic-client 1.0.0

package/dist/esm/models/Format.d.ts

@@ -0,0 +1,81 @@
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the Basic Meeting List Toolbox (BMLT) Semantic Interface for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **PHP array syntax** — repeatable array parameters use trailing `[]` in the name (`weekdays[]=2&weekdays[]=3`). The parameter names in this spec preserve the brackets so generated clients emit them. - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface Format
+ */
+export interface Format {
+    [key: string]: any | any;
+    /**
+     *
+     * @type {string}
+     * @memberof Format
+     */
+    keyString?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Format
+     */
+    nameString?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Format
+     */
+    descriptionString?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Format
+     */
+    lang?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Format
+     */
+    id?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Format
+     */
+    worldId?: string;
+    /**
+     * Aggregator mode only.
+     * @type {string}
+     * @memberof Format
+     */
+    rootServerId?: string;
+    /**
+     * Aggregator mode only.
+     * @type {string}
+     * @memberof Format
+     */
+    rootServerUri?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Format
+     */
+    formatTypeEnum?: string;
+}
+/**
+ * Check if a given object implements the Format interface.
+ */
+export declare function instanceOfFormat(value: object): value is Format;
+export declare function FormatFromJSON(json: any): Format;
+export declare function FormatFromJSONTyped(json: any, ignoreDiscriminator: boolean): Format;
+export declare function FormatToJSON(json: any): Format;
+export declare function FormatToJSONTyped(value?: Format | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/Format.js

@@ -0,0 +1,37 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the Basic Meeting List Toolbox (BMLT) Semantic Interface for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **PHP array syntax** — repeatable array parameters use trailing `[]` in the name (`weekdays[]=2&weekdays[]=3`). The parameter names in this spec preserve the brackets so generated clients emit them. - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ * Check if a given object implements the Format interface.
+ */
+export function instanceOfFormat(value) {
+    return true;
+}
+export function FormatFromJSON(json) {
+    return FormatFromJSONTyped(json, false);
+}
+export function FormatFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    return Object.assign(Object.assign({}, json), { 'keyString': json['key_string'] == null ? undefined : json['key_string'], 'nameString': json['name_string'] == null ? undefined : json['name_string'], 'descriptionString': json['description_string'] == null ? undefined : json['description_string'], 'lang': json['lang'] == null ? undefined : json['lang'], 'id': json['id'] == null ? undefined : json['id'], 'worldId': json['world_id'] == null ? undefined : json['world_id'], 'rootServerId': json['root_server_id'] == null ? undefined : json['root_server_id'], 'rootServerUri': json['root_server_uri'] == null ? undefined : json['root_server_uri'], 'formatTypeEnum': json['format_type_enum'] == null ? undefined : json['format_type_enum'] });
+}
+export function FormatToJSON(json) {
+    return FormatToJSONTyped(json, false);
+}
+export function FormatToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    return Object.assign(Object.assign({}, value), { 'key_string': value['keyString'], 'name_string': value['nameString'], 'description_string': value['descriptionString'], 'lang': value['lang'], 'id': value['id'], 'world_id': value['worldId'], 'root_server_id': value['rootServerId'], 'root_server_uri': value['rootServerUri'], 'format_type_enum': value['formatTypeEnum'] });
+}

package/dist/esm/models/GetCoverageArea200Response.d.ts

@@ -0,0 +1,50 @@
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface GetCoverageArea200Response
+ */
+export interface GetCoverageArea200Response {
+    /**
+     *
+     * @type {number}
+     * @memberof GetCoverageArea200Response
+     */
+    nwCornerLongitude?: number;
+    /**
+     *
+     * @type {number}
+     * @memberof GetCoverageArea200Response
+     */
+    nwCornerLatitude?: number;
+    /**
+     *
+     * @type {number}
+     * @memberof GetCoverageArea200Response
+     */
+    seCornerLongitude?: number;
+    /**
+     *
+     * @type {number}
+     * @memberof GetCoverageArea200Response
+     */
+    seCornerLatitude?: number;
+}
+/**
+ * Check if a given object implements the GetCoverageArea200Response interface.
+ */
+export declare function instanceOfGetCoverageArea200Response(value: object): value is GetCoverageArea200Response;
+export declare function GetCoverageArea200ResponseFromJSON(json: any): GetCoverageArea200Response;
+export declare function GetCoverageArea200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): GetCoverageArea200Response;
+export declare function GetCoverageArea200ResponseToJSON(json: any): GetCoverageArea200Response;
+export declare function GetCoverageArea200ResponseToJSONTyped(value?: GetCoverageArea200Response | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/GetCoverageArea200Response.js

@@ -0,0 +1,47 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ * Check if a given object implements the GetCoverageArea200Response interface.
+ */
+export function instanceOfGetCoverageArea200Response(value) {
+    return true;
+}
+export function GetCoverageArea200ResponseFromJSON(json) {
+    return GetCoverageArea200ResponseFromJSONTyped(json, false);
+}
+export function GetCoverageArea200ResponseFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    return {
+        'nwCornerLongitude': json['nw_corner_longitude'] == null ? undefined : json['nw_corner_longitude'],
+        'nwCornerLatitude': json['nw_corner_latitude'] == null ? undefined : json['nw_corner_latitude'],
+        'seCornerLongitude': json['se_corner_longitude'] == null ? undefined : json['se_corner_longitude'],
+        'seCornerLatitude': json['se_corner_latitude'] == null ? undefined : json['se_corner_latitude'],
+    };
+}
+export function GetCoverageArea200ResponseToJSON(json) {
+    return GetCoverageArea200ResponseToJSONTyped(json, false);
+}
+export function GetCoverageArea200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    return {
+        'nw_corner_longitude': value['nwCornerLongitude'],
+        'nw_corner_latitude': value['nwCornerLatitude'],
+        'se_corner_longitude': value['seCornerLongitude'],
+        'se_corner_latitude': value['seCornerLatitude'],
+    };
+}

package/dist/esm/models/GetFieldKeys200ResponseInner.d.ts

@@ -0,0 +1,38 @@
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface GetFieldKeys200ResponseInner
+ */
+export interface GetFieldKeys200ResponseInner {
+    /**
+     *
+     * @type {string}
+     * @memberof GetFieldKeys200ResponseInner
+     */
+    key?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof GetFieldKeys200ResponseInner
+     */
+    description?: string;
+}
+/**
+ * Check if a given object implements the GetFieldKeys200ResponseInner interface.
+ */
+export declare function instanceOfGetFieldKeys200ResponseInner(value: object): value is GetFieldKeys200ResponseInner;
+export declare function GetFieldKeys200ResponseInnerFromJSON(json: any): GetFieldKeys200ResponseInner;
+export declare function GetFieldKeys200ResponseInnerFromJSONTyped(json: any, ignoreDiscriminator: boolean): GetFieldKeys200ResponseInner;
+export declare function GetFieldKeys200ResponseInnerToJSON(json: any): GetFieldKeys200ResponseInner;
+export declare function GetFieldKeys200ResponseInnerToJSONTyped(value?: GetFieldKeys200ResponseInner | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/GetFieldKeys200ResponseInner.js

@@ -0,0 +1,43 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ * Check if a given object implements the GetFieldKeys200ResponseInner interface.
+ */
+export function instanceOfGetFieldKeys200ResponseInner(value) {
+    return true;
+}
+export function GetFieldKeys200ResponseInnerFromJSON(json) {
+    return GetFieldKeys200ResponseInnerFromJSONTyped(json, false);
+}
+export function GetFieldKeys200ResponseInnerFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    return {
+        'key': json['key'] == null ? undefined : json['key'],
+        'description': json['description'] == null ? undefined : json['description'],
+    };
+}
+export function GetFieldKeys200ResponseInnerToJSON(json) {
+    return GetFieldKeys200ResponseInnerToJSONTyped(json, false);
+}
+export function GetFieldKeys200ResponseInnerToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    return {
+        'key': value['key'],
+        'description': value['description'],
+    };
+}

package/dist/esm/models/GetFieldValues200ResponseInner.d.ts

@@ -0,0 +1,38 @@
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ *
+ * @export
+ * @interface GetFieldValues200ResponseInner
+ */
+export interface GetFieldValues200ResponseInner {
+    /**
+     *
+     * @type {string}
+     * @memberof GetFieldValues200ResponseInner
+     */
+    ids?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof GetFieldValues200ResponseInner
+     */
+    meetingKeyValue?: string;
+}
+/**
+ * Check if a given object implements the GetFieldValues200ResponseInner interface.
+ */
+export declare function instanceOfGetFieldValues200ResponseInner(value: object): value is GetFieldValues200ResponseInner;
+export declare function GetFieldValues200ResponseInnerFromJSON(json: any): GetFieldValues200ResponseInner;
+export declare function GetFieldValues200ResponseInnerFromJSONTyped(json: any, ignoreDiscriminator: boolean): GetFieldValues200ResponseInner;
+export declare function GetFieldValues200ResponseInnerToJSON(json: any): GetFieldValues200ResponseInner;
+export declare function GetFieldValues200ResponseInnerToJSONTyped(value?: GetFieldValues200ResponseInner | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/GetFieldValues200ResponseInner.js

@@ -0,0 +1,43 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+/**
+ * Check if a given object implements the GetFieldValues200ResponseInner interface.
+ */
+export function instanceOfGetFieldValues200ResponseInner(value) {
+    return true;
+}
+export function GetFieldValues200ResponseInnerFromJSON(json) {
+    return GetFieldValues200ResponseInnerFromJSONTyped(json, false);
+}
+export function GetFieldValues200ResponseInnerFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    return {
+        'ids': json['ids'] == null ? undefined : json['ids'],
+        'meetingKeyValue': json['meeting_key_value'] == null ? undefined : json['meeting_key_value'],
+    };
+}
+export function GetFieldValues200ResponseInnerToJSON(json) {
+    return GetFieldValues200ResponseInnerToJSONTyped(json, false);
+}
+export function GetFieldValues200ResponseInnerToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    return {
+        'ids': value['ids'],
+        'meeting_key_value': value['meetingKeyValue'],
+    };
+}

package/dist/esm/models/GetSearchResults200Response.d.ts

@@ -0,0 +1,24 @@
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { SemanticFormat } from './SemanticFormat';
+import type { SemanticMeeting } from './SemanticMeeting';
+import type { GetSearchResults200ResponseOneOf } from './GetSearchResults200ResponseOneOf';
+/**
+ * @type GetSearchResults200Response
+ *
+ * @export
+ */
+export type GetSearchResults200Response = Array<SemanticFormat> | Array<SemanticMeeting> | GetSearchResults200ResponseOneOf;
+export declare function GetSearchResults200ResponseFromJSON(json: any): GetSearchResults200Response;
+export declare function GetSearchResults200ResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): GetSearchResults200Response;
+export declare function GetSearchResults200ResponseToJSON(json: any): any;
+export declare function GetSearchResults200ResponseToJSONTyped(value?: GetSearchResults200Response | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/GetSearchResults200Response.js

@@ -0,0 +1,68 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import { instanceOfSemanticFormat, SemanticFormatFromJSONTyped, SemanticFormatToJSON, } from './SemanticFormat';
+import { instanceOfSemanticMeeting, SemanticMeetingFromJSONTyped, SemanticMeetingToJSON, } from './SemanticMeeting';
+import { instanceOfGetSearchResults200ResponseOneOf, GetSearchResults200ResponseOneOfFromJSONTyped, GetSearchResults200ResponseOneOfToJSON, } from './GetSearchResults200ResponseOneOf';
+export function GetSearchResults200ResponseFromJSON(json) {
+    return GetSearchResults200ResponseFromJSONTyped(json, false);
+}
+export function GetSearchResults200ResponseFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    if (typeof json !== 'object') {
+        return json;
+    }
+    if (instanceOfGetSearchResults200ResponseOneOf(json)) {
+        return GetSearchResults200ResponseOneOfFromJSONTyped(json, true);
+    }
+    if (Array.isArray(json)) {
+        if (json.every(item => typeof item === 'object')) {
+            if (json.every(item => instanceOfSemanticFormat(item))) {
+                return json.map(value => SemanticFormatFromJSONTyped(value, true));
+            }
+            if (json.every(item => instanceOfSemanticMeeting(item))) {
+                return json.map(value => SemanticMeetingFromJSONTyped(value, true));
+            }
+        }
+        return json;
+    }
+    return {};
+}
+export function GetSearchResults200ResponseToJSON(json) {
+    return GetSearchResults200ResponseToJSONTyped(json, false);
+}
+export function GetSearchResults200ResponseToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    if (typeof value !== 'object') {
+        return value;
+    }
+    if (instanceOfGetSearchResults200ResponseOneOf(value)) {
+        return GetSearchResults200ResponseOneOfToJSON(value);
+    }
+    if (Array.isArray(value)) {
+        if (value.every(item => typeof item === 'object')) {
+            if (value.every(item => instanceOfSemanticFormat(item))) {
+                return value.map(value => SemanticFormatToJSON(value));
+            }
+            if (value.every(item => instanceOfSemanticMeeting(item))) {
+                return value.map(value => SemanticMeetingToJSON(value));
+            }
+        }
+        return value;
+    }
+    return {};
+}

package/dist/esm/models/GetSearchResults200ResponseOneOf.d.ts

@@ -0,0 +1,40 @@
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import type { SemanticFormat } from './SemanticFormat';
+import type { SemanticMeeting } from './SemanticMeeting';
+/**
+ *
+ * @export
+ * @interface GetSearchResults200ResponseOneOf
+ */
+export interface GetSearchResults200ResponseOneOf {
+    /**
+     *
+     * @type {Array<SemanticMeeting>}
+     * @memberof GetSearchResults200ResponseOneOf
+     */
+    meetings?: Array<SemanticMeeting>;
+    /**
+     *
+     * @type {Array<SemanticFormat>}
+     * @memberof GetSearchResults200ResponseOneOf
+     */
+    formats?: Array<SemanticFormat>;
+}
+/**
+ * Check if a given object implements the GetSearchResults200ResponseOneOf interface.
+ */
+export declare function instanceOfGetSearchResults200ResponseOneOf(value: object): value is GetSearchResults200ResponseOneOf;
+export declare function GetSearchResults200ResponseOneOfFromJSON(json: any): GetSearchResults200ResponseOneOf;
+export declare function GetSearchResults200ResponseOneOfFromJSONTyped(json: any, ignoreDiscriminator: boolean): GetSearchResults200ResponseOneOf;
+export declare function GetSearchResults200ResponseOneOfToJSON(json: any): GetSearchResults200ResponseOneOf;
+export declare function GetSearchResults200ResponseOneOfToJSONTyped(value?: GetSearchResults200ResponseOneOf | null, ignoreDiscriminator?: boolean): any;

package/dist/esm/models/GetSearchResults200ResponseOneOf.js

@@ -0,0 +1,45 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * BMLT Semantic API
+ * OpenAPI description of the BMLT Semantic Interface (the read-only meeting-query API) for the JSON data format.  The semantic interface dispatches all operations from a single endpoint (`/client_interface/json/`) using a `switcher` query parameter. To keep each operation discoverable, this spec models each `switcher` value as a distinct path key with the query string baked in. Tools such as Swagger UI, Redoc, and openapi-generator handle these path keys correctly even though the OpenAPI spec technically expects unique URL paths.  ### Things that do not map cleanly onto OpenAPI  - **Sign-as-operator** — many filters (`formats`, `services`, `weekdays`, `venue_types`, `meeting_ids`, `root_server_ids`, `format_ids`) use *positive* values to include and *negative* values to exclude. JSON Schema cannot enforce that semantics; it is documented per parameter. - **Cross-parameter constraints** — in aggregator mode `GetSearchResults` requires at least one filter parameter. Invalid combinations typically return an empty array `[]` instead of an HTTP error. - **Empty-array errors** — many endpoints return `[]` for invalid input rather than a 4xx response body.
+ *
+ * The version of the OpenAPI document: 1.0.0
+ *
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+import { SemanticFormatFromJSON, SemanticFormatToJSON, } from './SemanticFormat';
+import { SemanticMeetingFromJSON, SemanticMeetingToJSON, } from './SemanticMeeting';
+/**
+ * Check if a given object implements the GetSearchResults200ResponseOneOf interface.
+ */
+export function instanceOfGetSearchResults200ResponseOneOf(value) {
+    return true;
+}
+export function GetSearchResults200ResponseOneOfFromJSON(json) {
+    return GetSearchResults200ResponseOneOfFromJSONTyped(json, false);
+}
+export function GetSearchResults200ResponseOneOfFromJSONTyped(json, ignoreDiscriminator) {
+    if (json == null) {
+        return json;
+    }
+    return {
+        'meetings': json['meetings'] == null ? undefined : (json['meetings'].map(SemanticMeetingFromJSON)),
+        'formats': json['formats'] == null ? undefined : (json['formats'].map(SemanticFormatFromJSON)),
+    };
+}
+export function GetSearchResults200ResponseOneOfToJSON(json) {
+    return GetSearchResults200ResponseOneOfToJSONTyped(json, false);
+}
+export function GetSearchResults200ResponseOneOfToJSONTyped(value, ignoreDiscriminator = false) {
+    if (value == null) {
+        return value;
+    }
+    return {
+        'meetings': value['meetings'] == null ? undefined : (value['meetings'].map(SemanticMeetingToJSON)),
+        'formats': value['formats'] == null ? undefined : (value['formats'].map(SemanticFormatToJSON)),
+    };
+}