conductor-node 4.0.2 → 4.0.3

package/dist/package.json

@@ -1,6 +1,6 @@
 {
     "name": "conductor-node",
-    "version": "4.0.2",
+    "version": "4.0.3",
     "description": "Easily integrate with the entire QuickBooks Desktop API with fully-type async TypeScript",
     "author": "Danny Nemer <hi@DannyNemer.com>",
     "license": "MIT",

package/dist/src/integrations/qbd/qbdTypes.d.ts

@@ -161,7 +161,7 @@ export interface AccountQueryRq {
     OwnerID?: string[] | string;
 }
 export interface AccountQueryRs {
-    AccountRet: [AccountRet, ...AccountRet[]];
+    AccountRet: AccountRet[];
 }
 export interface AccountRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
@@ -623,7 +623,7 @@ export interface BillPaymentCheckQueryRq {
     OwnerID?: string[] | string;
 }
 export interface BillPaymentCheckQueryRs {
-    BillPaymentCheckRet: [BillPaymentCheckRet, ...BillPaymentCheckRet[]];
+    BillPaymentCheckRet: BillPaymentCheckRet[];
 }
 export interface BillPaymentCheckRet {
     /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
@@ -730,7 +730,7 @@ export interface BillQueryRq {
     OwnerID?: string[] | string;
 }
 export interface BillQueryRs {
-    BillRet: [BillRet, ...BillRet[]];
+    BillRet: BillRet[];
 }
 export interface BillRet {
     /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests.
@@ -954,7 +954,7 @@ export interface CheckQueryRq {
     OwnerID?: string[] | string;
 }
 export interface CheckQueryRs {
-    CheckRet: [CheckRet, ...CheckRet[]];
+    CheckRet: CheckRet[];
 }
 export interface CheckRet {
     /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
@@ -1077,7 +1077,7 @@ export interface ClassQueryRq {
     IncludeRetElement?: string[] | string;
 }
 export interface ClassQueryRs {
-    ClassRet: [ClassRet, ...ClassRet[]];
+    ClassRet: ClassRet[];
 }
 export interface ClassRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
@@ -1430,7 +1430,7 @@ export interface CustomerQueryRq {
     OwnerID?: string[] | string;
 }
 export interface CustomerQueryRs {
-    CustomerRet: [CustomerRet, ...CustomerRet[]];
+    CustomerRet: CustomerRet[];
 }
 export interface CustomerRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
@@ -1745,7 +1745,7 @@ export interface DepositQueryRq {
     OwnerID?: string[] | string;
 }
 export interface DepositQueryRs {
-    DepositRet: [DepositRet, ...DepositRet[]];
+    DepositRet: DepositRet[];
 }
 export interface DepositRet {
     /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
@@ -2089,7 +2089,7 @@ export interface EmployeeQueryRq {
     OwnerID?: string[] | string;
 }
 export interface EmployeeQueryRs {
-    EmployeeRet: [EmployeeRet, ...EmployeeRet[]];
+    EmployeeRet: EmployeeRet[];
 }
 export interface EmployeeRet {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
@@ -2741,7 +2741,7 @@ export interface ItemServiceQueryRq {
     OwnerID?: string[] | string;
 }
 export interface ItemServiceQueryRs {
-    ItemServiceRet: [ItemServiceRet, ...ItemServiceRet[]];
+    ItemServiceRet: ItemServiceRet[];
 }
 export interface ItemServiceRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
@@ -2922,7 +2922,7 @@ export interface JournalEntryQueryRq {
     OwnerID?: string[] | string;
 }
 export interface JournalEntryQueryRs {
-    JournalEntryRet: [JournalEntryRet, ...JournalEntryRet[]];
+    JournalEntryRet: JournalEntryRet[];
 }
 export interface JournalEntryRet {
     /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
@@ -3442,7 +3442,7 @@ export interface TimeTrackingQueryRq {
     IncludeRetElement?: string[] | string;
 }
 export interface TimeTrackingQueryRs {
-    TimeTrackingRet: [TimeTrackingRet, ...TimeTrackingRet[]];
+    TimeTrackingRet: TimeTrackingRet[];
 }
 export interface TimeTrackingRet {
     /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
@@ -3795,7 +3795,7 @@ export interface VendorQueryRq {
     OwnerID?: string[] | string;
 }
 export interface VendorQueryRs {
-    VendorRet: [VendorRet, ...VendorRet[]];
+    VendorRet: VendorRet[];
 }
 export interface VendorRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */

package/dist/src/testUtils.d.ts

@@ -1,2 +1,2 @@
-export declare const MOCK_CLIENT_API_KEY = "mock_client_api_key";
-export declare const MOCK_QBD_USER_CONNECTION_ID = "mock_qbd_user_connection_id";
+export declare const TEST_CLIENT_API_KEY = "test_client_api_key";
+export declare const TEST_QBD_CONNECTION_ID = "test_qbd_connection_id";

package/dist/src/testUtils.js

@@ -1,5 +1,5 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.MOCK_QBD_USER_CONNECTION_ID = exports.MOCK_CLIENT_API_KEY = void 0;
-exports.MOCK_CLIENT_API_KEY = "mock_client_api_key";
-exports.MOCK_QBD_USER_CONNECTION_ID = "mock_qbd_user_connection_id";
+exports.TEST_QBD_CONNECTION_ID = exports.TEST_CLIENT_API_KEY = void 0;
+exports.TEST_CLIENT_API_KEY = "test_client_api_key";
+exports.TEST_QBD_CONNECTION_ID = "test_qbd_connection_id";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "conductor-node",
-  "version": "4.0.2",
+  "version": "4.0.3",
   "description": "Easily integrate with the entire QuickBooks Desktop API with fully-type async TypeScript",
   "author": "Danny Nemer <hi@DannyNemer.com>",
   "license": "MIT",