regenerate ts sdk.

sdk/typescript/lib/generated/.openapi-generator/FILES

@@ -61,19 +61,30 @@ models/ComponentEntityRoleAssignments.ts
 models/ComponentMethodRoyalty.ts
 models/ComponentRoyaltyConfig.ts
 models/CursorLimitMixin.ts
+models/DetailedEventEmitter.ts
+models/DetailedEventEmitterBase.ts
+models/DetailedEventIdentifier.ts
+models/DetailedEventPayload.ts
+models/DetailedEventPayloadTypeDefinition.ts
+models/DetailedEventPayloadTypeDefinitionBase.ts
+models/DetailedEventsItem.ts
 models/EntityMetadataCollection.ts
 models/EntityMetadataCollectionAllOf.ts
 models/EntityMetadataItem.ts
 models/EntityMetadataItemValue.ts
 models/EntityMetadataItemValueAllOf.ts
+models/EntityMethodEventEmitter.ts
+models/EntityMethodEventEmitterAllOf.ts
 models/EntityNotFoundError.ts
 models/EntityNotFoundErrorAllOf.ts
 models/EntitySchemaCollection.ts
 models/EntitySchemaCollectionAllOf.ts
 models/EntitySchemaCollectionItem.ts
 models/ErrorResponse.ts
+models/EventEmitterType.ts
 models/EventsItem.ts
 models/FromLedgerStateMixin.ts
+models/FunctionEmitter.ts
 models/FungibleResourcesCollection.ts
 models/FungibleResourcesCollectionAllOf.ts
 models/FungibleResourcesCollectionItem.ts
@@ -171,6 +182,7 @@ models/MetadataUrlArrayValueAllOf.ts
 models/MetadataUrlValue.ts
 models/MetadataUrlValueAllOf.ts
 models/MetadataValueType.ts
+models/MethodEmitter.ts
 models/NativeResourceAccessControllerRecoveryBadgeValue.ts
 models/NativeResourceAccessControllerRecoveryBadgeValueAllOf.ts
 models/NativeResourceAccountOwnerBadgeValue.ts
@@ -235,6 +247,8 @@ models/PackageBlueprintCollectionItem.ts
 models/PackageCodeCollection.ts
 models/PackageCodeCollectionAllOf.ts
 models/PackageCodeCollectionItem.ts
+models/PackageFunctionEventEmitter.ts
+models/PackageFunctionEventEmitterAllOf.ts
 models/PackageVmType.ts
 models/PreviewFlags.ts
 models/PreviewTransaction.ts
@@ -319,6 +333,9 @@ models/ResultSetCursorMixin.ts
 models/RoleAssignmentResolution.ts
 models/RoleKey.ts
 models/RoyaltyAmount.ts
+models/SborTypeKind.ts
+models/SchemaLocalEventPayloadTypeDefinition.ts
+models/SchemaLocalEventPayloadTypeDefinitionAllOf.ts
 models/ScryptoSborValue.ts
 models/StateAccountAuthorizedDepositorsPageRequest.ts
 models/StateAccountAuthorizedDepositorsPageResponse.ts
@@ -477,5 +494,7 @@ models/ValidatorsUptimeRequest.ts
 models/ValidatorsUptimeRequestAllOf.ts
 models/ValidatorsUptimeResponse.ts
 models/ValidatorsUptimeResponseAllOf.ts
+models/WellKnownEventPayloadTypeDefinition.ts
+models/WellKnownEventPayloadTypeDefinitionAllOf.ts
 models/index.ts
 runtime.ts

sdk/typescript/lib/generated/models/DetailedEventEmitter.ts

@@ -0,0 +1,72 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Radix Gateway API - Babylon
+ * This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic state on the RadixDLT ledger, and intelligently handle transaction submission.  It is designed for use by wallets and explorers, and for light queries from front-end dApps. For exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using the Core API on a Node. A Gateway is only needed for reading historic snapshots of ledger states or a more robust set-up.  The Gateway API is implemented by the [Network Gateway](https://github.com/radixdlt/babylon-gateway), which is configured to read from [full node(s)](https://github.com/radixdlt/babylon-node) to extract and index data from the network.  This document is an API reference documentation, visit [User Guide](https://docs.radixdlt.com/) to learn more about how to run a Gateway of your own.  ## Migration guide  Please see [the latest release notes](https://github.com/radixdlt/babylon-gateway/releases).  ## Integration and forward compatibility guarantees  All responses may have additional fields added at any release, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects.  When the Radix protocol is updated, new functionality may be added, and so discriminated unions returned by the API may need to be updated to have new variants added, corresponding to the updated data. Clients may need to update in advance to be able to handle these new variants when a protocol update comes out.  On the very rare occasions we need to make breaking changes to the API, these will be warned in advance with deprecation notices on previous versions. These deprecation notices will include a safe migration path. Deprecation notes or breaking changes will be flagged clearly in release notes for new versions of the Gateway.  The Gateway DB schema is not subject to any compatibility guarantees, and may be changed at any release. DB changes will be flagged in the release notes so clients doing custom DB integrations can prepare. 
+ *
+ * The version of the OpenAPI document: v1.10.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 {
+    EntityMethodEventEmitter,
+    instanceOfEntityMethodEventEmitter,
+    EntityMethodEventEmitterFromJSON,
+    EntityMethodEventEmitterFromJSONTyped,
+    EntityMethodEventEmitterToJSON,
+} from './EntityMethodEventEmitter';
+import {
+    PackageFunctionEventEmitter,
+    instanceOfPackageFunctionEventEmitter,
+    PackageFunctionEventEmitterFromJSON,
+    PackageFunctionEventEmitterFromJSONTyped,
+    PackageFunctionEventEmitterToJSON,
+} from './PackageFunctionEventEmitter';
+
+/**
+ * @type DetailedEventEmitter
+ * 
+ * @export
+ */
+export type DetailedEventEmitter = { type: 'EntityMethod' } & EntityMethodEventEmitter | { type: 'PackageFunction' } & PackageFunctionEventEmitter;
+
+export function DetailedEventEmitterFromJSON(json: any): DetailedEventEmitter {
+    return DetailedEventEmitterFromJSONTyped(json, false);
+}
+
+export function DetailedEventEmitterFromJSONTyped(json: any, ignoreDiscriminator: boolean): DetailedEventEmitter {
+    if ((json === undefined) || (json === null)) {
+        return json;
+    }
+    switch (json['type']) {
+        case 'EntityMethod':
+            return {...EntityMethodEventEmitterFromJSONTyped(json, true), type: 'EntityMethod'};
+        case 'PackageFunction':
+            return {...PackageFunctionEventEmitterFromJSONTyped(json, true), type: 'PackageFunction'};
+        default:
+            throw new Error(`No variant of DetailedEventEmitter exists with 'type=${json['type']}'`);
+    }
+}
+
+export function DetailedEventEmitterToJSON(value?: DetailedEventEmitter | null): any {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    switch (value['type']) {
+        case 'EntityMethod':
+            return EntityMethodEventEmitterToJSON(value);
+        case 'PackageFunction':
+            return PackageFunctionEventEmitterToJSON(value);
+        default:
+            throw new Error(`No variant of DetailedEventEmitter exists with 'type=${value['type']}'`);
+    }
+
+}
+

sdk/typescript/lib/generated/models/DetailedEventEmitterBase.ts

@@ -0,0 +1,73 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Radix Gateway API - Babylon
+ * This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic state on the RadixDLT ledger, and intelligently handle transaction submission.  It is designed for use by wallets and explorers, and for light queries from front-end dApps. For exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using the Core API on a Node. A Gateway is only needed for reading historic snapshots of ledger states or a more robust set-up.  The Gateway API is implemented by the [Network Gateway](https://github.com/radixdlt/babylon-gateway), which is configured to read from [full node(s)](https://github.com/radixdlt/babylon-node) to extract and index data from the network.  This document is an API reference documentation, visit [User Guide](https://docs.radixdlt.com/) to learn more about how to run a Gateway of your own.  ## Migration guide  Please see [the latest release notes](https://github.com/radixdlt/babylon-gateway/releases).  ## Integration and forward compatibility guarantees  All responses may have additional fields added at any release, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects.  When the Radix protocol is updated, new functionality may be added, and so discriminated unions returned by the API may need to be updated to have new variants added, corresponding to the updated data. Clients may need to update in advance to be able to handle these new variants when a protocol update comes out.  On the very rare occasions we need to make breaking changes to the API, these will be warned in advance with deprecation notices on previous versions. These deprecation notices will include a safe migration path. Deprecation notes or breaking changes will be flagged clearly in release notes for new versions of the Gateway.  The Gateway DB schema is not subject to any compatibility guarantees, and may be changed at any release. DB changes will be flagged in the release notes so clients doing custom DB integrations can prepare. 
+ *
+ * The version of the OpenAPI document: v1.10.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 { exists, mapValues } from '../runtime';
+import type { EventEmitterType } from './EventEmitterType';
+import {
+    EventEmitterTypeFromJSON,
+    EventEmitterTypeFromJSONTyped,
+    EventEmitterTypeToJSON,
+} from './EventEmitterType';
+
+/**
+ * Detailed information about the event emitter.
+ * @export
+ * @interface DetailedEventEmitterBase
+ */
+export interface DetailedEventEmitterBase {
+    /**
+     * 
+     * @type {EventEmitterType}
+     * @memberof DetailedEventEmitterBase
+     */
+    type: EventEmitterType;
+}
+
+/**
+ * Check if a given object implements the DetailedEventEmitterBase interface.
+ */
+export function instanceOfDetailedEventEmitterBase(value: object): boolean {
+    let isInstance = true;
+    isInstance = isInstance && "type" in value;
+
+    return isInstance;
+}
+
+export function DetailedEventEmitterBaseFromJSON(json: any): DetailedEventEmitterBase {
+    return DetailedEventEmitterBaseFromJSONTyped(json, false);
+}
+
+export function DetailedEventEmitterBaseFromJSONTyped(json: any, ignoreDiscriminator: boolean): DetailedEventEmitterBase {
+    if ((json === undefined) || (json === null)) {
+        return json;
+    }
+    return {
+
+        'type': EventEmitterTypeFromJSON(json['type']),
+    };
+}
+
+export function DetailedEventEmitterBaseToJSON(value?: DetailedEventEmitterBase | null): any {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+
+        'type': EventEmitterTypeToJSON(value.type),
+    };
+}
+

sdk/typescript/lib/generated/models/DetailedEventIdentifier.ts

@@ -0,0 +1,87 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Radix Gateway API - Babylon
+ * This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic state on the RadixDLT ledger, and intelligently handle transaction submission.  It is designed for use by wallets and explorers, and for light queries from front-end dApps. For exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using the Core API on a Node. A Gateway is only needed for reading historic snapshots of ledger states or a more robust set-up.  The Gateway API is implemented by the [Network Gateway](https://github.com/radixdlt/babylon-gateway), which is configured to read from [full node(s)](https://github.com/radixdlt/babylon-node) to extract and index data from the network.  This document is an API reference documentation, visit [User Guide](https://docs.radixdlt.com/) to learn more about how to run a Gateway of your own.  ## Migration guide  Please see [the latest release notes](https://github.com/radixdlt/babylon-gateway/releases).  ## Integration and forward compatibility guarantees  All responses may have additional fields added at any release, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects.  When the Radix protocol is updated, new functionality may be added, and so discriminated unions returned by the API may need to be updated to have new variants added, corresponding to the updated data. Clients may need to update in advance to be able to handle these new variants when a protocol update comes out.  On the very rare occasions we need to make breaking changes to the API, these will be warned in advance with deprecation notices on previous versions. These deprecation notices will include a safe migration path. Deprecation notes or breaking changes will be flagged clearly in release notes for new versions of the Gateway.  The Gateway DB schema is not subject to any compatibility guarantees, and may be changed at any release. DB changes will be flagged in the release notes so clients doing custom DB integrations can prepare. 
+ *
+ * The version of the OpenAPI document: v1.10.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 { exists, mapValues } from '../runtime';
+/**
+ * Identifier of an event.
+ * @export
+ * @interface DetailedEventIdentifier
+ */
+export interface DetailedEventIdentifier {
+    /**
+     * The address of the published package that defines the event.
+
+Bech32m-encoded human readable version of the address.
+
+     * @type {string}
+     * @memberof DetailedEventIdentifier
+     */
+    _package: string;
+    /**
+     * The blueprint that defines the event.
+     * @type {string}
+     * @memberof DetailedEventIdentifier
+     */
+    blueprint: string;
+    /**
+     * Event name.
+     * @type {string}
+     * @memberof DetailedEventIdentifier
+     */
+    event: string;
+}
+
+/**
+ * Check if a given object implements the DetailedEventIdentifier interface.
+ */
+export function instanceOfDetailedEventIdentifier(value: object): boolean {
+    let isInstance = true;
+    isInstance = isInstance && "_package" in value;
+    isInstance = isInstance && "blueprint" in value;
+    isInstance = isInstance && "event" in value;
+
+    return isInstance;
+}
+
+export function DetailedEventIdentifierFromJSON(json: any): DetailedEventIdentifier {
+    return DetailedEventIdentifierFromJSONTyped(json, false);
+}
+
+export function DetailedEventIdentifierFromJSONTyped(json: any, ignoreDiscriminator: boolean): DetailedEventIdentifier {
+    if ((json === undefined) || (json === null)) {
+        return json;
+    }
+    return {
+
+        '_package': json['package'],
+        'blueprint': json['blueprint'],
+        'event': json['event'],
+    };
+}
+
+export function DetailedEventIdentifierToJSON(value?: DetailedEventIdentifier | null): any {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+
+        'package': value._package,
+        'blueprint': value.blueprint,
+        'event': value.event,
+    };
+}
+

sdk/typescript/lib/generated/models/DetailedEventPayload.ts

@@ -0,0 +1,66 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Radix Gateway API - Babylon
+ * This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic state on the RadixDLT ledger, and intelligently handle transaction submission.  It is designed for use by wallets and explorers, and for light queries from front-end dApps. For exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using the Core API on a Node. A Gateway is only needed for reading historic snapshots of ledger states or a more robust set-up.  The Gateway API is implemented by the [Network Gateway](https://github.com/radixdlt/babylon-gateway), which is configured to read from [full node(s)](https://github.com/radixdlt/babylon-node) to extract and index data from the network.  This document is an API reference documentation, visit [User Guide](https://docs.radixdlt.com/) to learn more about how to run a Gateway of your own.  ## Migration guide  Please see [the latest release notes](https://github.com/radixdlt/babylon-gateway/releases).  ## Integration and forward compatibility guarantees  All responses may have additional fields added at any release, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects.  When the Radix protocol is updated, new functionality may be added, and so discriminated unions returned by the API may need to be updated to have new variants added, corresponding to the updated data. Clients may need to update in advance to be able to handle these new variants when a protocol update comes out.  On the very rare occasions we need to make breaking changes to the API, these will be warned in advance with deprecation notices on previous versions. These deprecation notices will include a safe migration path. Deprecation notes or breaking changes will be flagged clearly in release notes for new versions of the Gateway.  The Gateway DB schema is not subject to any compatibility guarantees, and may be changed at any release. DB changes will be flagged in the release notes so clients doing custom DB integrations can prepare. 
+ *
+ * The version of the OpenAPI document: v1.10.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 { exists, mapValues } from '../runtime';
+/**
+ * Event payload decoded into Programmatic JSON using its schema.
+ * @export
+ * @interface DetailedEventPayload
+ */
+export interface DetailedEventPayload {
+    /**
+     * 
+     * @type {object}
+     * @memberof DetailedEventPayload
+     */
+    programmatic_json: object;
+}
+
+/**
+ * Check if a given object implements the DetailedEventPayload interface.
+ */
+export function instanceOfDetailedEventPayload(value: object): boolean {
+    let isInstance = true;
+    isInstance = isInstance && "programmatic_json" in value;
+
+    return isInstance;
+}
+
+export function DetailedEventPayloadFromJSON(json: any): DetailedEventPayload {
+    return DetailedEventPayloadFromJSONTyped(json, false);
+}
+
+export function DetailedEventPayloadFromJSONTyped(json: any, ignoreDiscriminator: boolean): DetailedEventPayload {
+    if ((json === undefined) || (json === null)) {
+        return json;
+    }
+    return {
+
+        'programmatic_json': json['programmatic_json'],
+    };
+}
+
+export function DetailedEventPayloadToJSON(value?: DetailedEventPayload | null): any {
+    if (value === undefined) {
+        return undefined;
+    }
+    if (value === null) {
+        return null;
+    }
+    return {
+
+        'programmatic_json': value.programmatic_json,
+    };
+}
+