@fluentcommerce/fc-connect-sdk 0.1.53 → 0.1.55

package/dist/types/auth/index.d.ts

@@ -0,0 +1,3 @@
+export { loadFluentProfile, listFluentProfiles, getFluentProfileInfo, resolveProfileBaseDir, } from './profile-loader';
+export type { FluentProfileOptions, FluentProfileInfo } from './profile-loader';
+export { OAuth2AuthProvider, BearerTokenAuthProvider, AuthManager, VersoriConnectionAdapter, type VersoriConnection, } from './auth-provider';

package/dist/types/auth/profile-loader.d.ts

@@ -0,0 +1,18 @@
+import { FluentClientConfig } from '../types';
+export interface FluentProfileOptions {
+    profileDir?: string;
+    retailer?: string;
+    timeout?: number;
+    retryConfig?: FluentClientConfig['retryConfig'];
+}
+export interface FluentProfileInfo {
+    name: string;
+    baseUrl: string;
+    accountId: string;
+    username: string;
+    retailers: string[];
+}
+export declare function resolveProfileBaseDir(options?: FluentProfileOptions): string;
+export declare function loadFluentProfile(profileName: string, options?: FluentProfileOptions): FluentClientConfig;
+export declare function listFluentProfiles(options?: FluentProfileOptions): string[];
+export declare function getFluentProfileInfo(profileName: string, options?: FluentProfileOptions): FluentProfileInfo | null;

package/dist/types/client-factory.d.ts

@@ -1,6 +1,7 @@
 import { FluentClient } from './clients/fluent-client';
 import { FluentVersoriClient } from './versori/fluent-versori-client';
 import { FluentClientConfig, Logger, ExecutionContext } from './types';
+import { type FluentProfileOptions } from './auth/profile-loader';
 export type ClientContext = {
     fetch: typeof fetch;
     log?: Logger;
@@ -24,3 +25,6 @@ export declare const isDirectContext: (context: ClientContext) => context is {
     config: FluentClientConfig;
     logger?: Logger;
 };
+export declare function createClientFromProfile(profileName: string, options?: FluentProfileOptions & CreateClientOptions & {
+    logger?: Logger;
+}): Promise<FluentClient>;

package/dist/types/index.d.ts

@@ -1,4 +1,4 @@
-export { createClient, isHttpContext, isDirectContext } from './client-factory';
+export { createClient, createClientFromProfile, isHttpContext, isDirectContext, } from './client-factory';
 export type { ClientContext, CreateClientOptions } from './client-factory';
 export { FluentClient } from './clients/fluent-client';
 export { FluentVersoriClient } from './versori/fluent-versori-client';
@@ -14,6 +14,8 @@ export { DataSourceType } from './types';
 export { parseAndValidateCsv, detectFileType, parseWebhookRequest, validateFluentEvent, validateGraphQLPayload, generateFileName, generateTimestampedFileName, generateFilePath, generateDateSubdirectories, extractFileName, extractFileExtension, replaceFileExtension, type FileNamingOptions, } from './utils';
 export { detectPaginationVariables, extractConnection, extractCursor, hasMorePages, buildPaginationVariables, type PaginationVariables, } from './utils/pagination-helpers';
 export { OAuth2AuthProvider, BearerTokenAuthProvider, AuthManager, VersoriConnectionAdapter, type VersoriConnection, } from './auth/auth-provider';
+export { loadFluentProfile, listFluentProfiles, getFluentProfileInfo, resolveProfileBaseDir, } from './auth/profile-loader';
+export type { FluentProfileOptions, FluentProfileInfo } from './auth/profile-loader';
 export { type FileDiscoveryStrategy, type FileDiscoveryContext, type FileParserStrategy, type TransformationStrategy, type TransformationContext, type IngestionValidationResult, type BatchSubmissionStrategy, type BatchSubmissionContext, type BatchSubmissionResult, type JobManagementStrategy, type JobContext, type JobStatus, type IngestionStrategy, type StrategyFactory, } from './services/orchestration/strategies/ingestion-strategies';
 export * from './errors/index';
 export { ConfigurationError, AggregateIngestionError, IngestionErrorFactory, } from './errors/ingestion-errors';

package/docs/00-START-HERE/EXPORT-VALIDATION.md

@@ -1,158 +1,158 @@
-# Export Validation Guide
-
-## Overview
-
-The SDK uses a validation script to ensure all public exports are properly re-exported through index files. This helps maintain a clean public API and ensures nothing is accidentally exposed or hidden.
-
-## Running Export Validation
-
-```bash
-cd fc-connect-sdk
-npm run validate:exports
-```
-
-This script:
-1. Scans all TypeScript files in `src/` to find exported items (classes, functions, types, interfaces, enums, constants)
-2. Checks if exports are re-exported through their module's `index.ts`
-3. Checks if module `index.ts` files are properly exported from main `index.ts`
-4. Reports missing exports
-
-## Understanding the Results
-
-The script reports three types of issues:
-
-### 1. Missing Module Exports
-
-**Meaning:** An export exists in a source file but is not re-exported through the module's `index.ts`.
-
-**Example:**
-```
-Export "MyClass" from "src/services/core/my-service.ts" is not exported from "src/services/core/index.ts"
-```
-
-**Action:** Add the export to the module's `index.ts`:
-```typescript
-// src/services/core/index.ts
-export { MyClass } from './my-service';
-```
-
-### 2. Missing Main Exports
-
-**Meaning:** A top-level export (file directly in `src/`) is not exported from `src/index.ts`.
-
-**Example:**
-```
-Export "MyUtility" from "src/my-utility.ts" is not exported from "src/index.ts"
-```
-
-**Action:** Add the export to `src/index.ts`:
-```typescript
-// src/index.ts
-export { MyUtility } from './my-utility';
-```
-
-### 3. Missing Main Module Exports
-
-**Meaning:** A module's `index.ts` is not exported from the main `index.ts`.
-
-**Example:**
-```
-Module index "src/services/core/index.ts" is not exported from main index.ts
-```
-
-**Action:** Add the module export to `src/index.ts`:
-```typescript
-// src/index.ts
-export * from './services/core';
-```
-
-### 4. Files Without Module Index
-
-**Meaning:** A file has exports but there's no `index.ts` in its directory.
-
-**Example:**
-```
-File "src/services/core/my-service.ts" has exports but no module index.ts found
-```
-
-**Action:** Either:
-- Create an `index.ts` in that directory and export from it
-- Or if it's a top-level file, export it directly from `src/index.ts`
-
-## Common Patterns
-
-### Pattern 1: Star Export (Recommended for Modules)
-
-```typescript
-// src/services/core/index.ts
-export * from './my-service';
-export * from './other-service';
-```
-
-**Note:** The script may report false positives for star exports because it can't always determine what's exported. If you see an issue but know the export is via `export *`, you can safely ignore it.
-
-### Pattern 2: Named Exports (Explicit Control)
-
-```typescript
-// src/services/core/index.ts
-export { MyClass, MyFunction } from './my-service';
-export type { MyType, MyInterface } from './my-service';
-```
-
-### Pattern 3: Re-exporting from Parent Module
-
-```typescript
-// src/services/index.ts
-export * from './core';
-export * from './batch';
-
-// src/index.ts
-export * from './services'; // This re-exports everything from services/core
-```
-
-## False Positives
-
-The script may report false positives in these cases:
-
-1. **Star Exports:** If a module uses `export * from './module'`, the script may not detect all re-exports
-2. **Internal Exports:** Some exports are intentionally internal and shouldn't be in the public API
-3. **Parent Module Re-exports:** If a parent module re-exports everything, child module exports are still accessible
-
-## Best Practices
-
-1. **Use Star Exports for Modules:** `export * from './module'` keeps index files clean
-2. **Explicit Exports for Public API:** Use named exports in `src/index.ts` for important public APIs
-3. **Internal Exports:** Don't export internal utilities from `src/index.ts`
-4. **Type Exports:** Use `export type` for type-only exports to enable tree-shaking
-
-## Integration with CI/CD
-
-Add export validation to your pre-publish checks:
-
-```json
-{
-  "scripts": {
-    "prepublishOnly": "npm run validate:exports && npm run build"
-  }
-}
-```
-
-## Troubleshooting
-
-### Script reports too many false positives
-
-The script uses regex parsing which may not catch all export patterns. If you're confident an export is properly re-exported via star exports, you can safely ignore the warning.
-
-### Need to exclude internal exports
-
-Currently, the script checks all exports. If you want to exclude certain files or exports, you can modify the script to skip specific patterns.
-
-### Module is exported but script doesn't detect it
-
-Check if the module is exported via a parent module's star export. The script checks direct exports but may miss transitive exports.
-
-## Related Documentation
-
-- [SDK Architecture](../04-REFERENCE/architecture/readme.md)
-- [API Reference](../02-CORE-GUIDES/api-reference/api-reference-readme.md)
-
+# Export Validation Guide
+
+## Overview
+
+The SDK uses a validation script to ensure all public exports are properly re-exported through index files. This helps maintain a clean public API and ensures nothing is accidentally exposed or hidden.
+
+## Running Export Validation
+
+```bash
+cd fc-connect-sdk
+npm run validate:exports
+```
+
+This script:
+1. Scans all TypeScript files in `src/` to find exported items (classes, functions, types, interfaces, enums, constants)
+2. Checks if exports are re-exported through their module's `index.ts`
+3. Checks if module `index.ts` files are properly exported from main `index.ts`
+4. Reports missing exports
+
+## Understanding the Results
+
+The script reports three types of issues:
+
+### 1. Missing Module Exports
+
+**Meaning:** An export exists in a source file but is not re-exported through the module's `index.ts`.
+
+**Example:**
+```
+Export "MyClass" from "src/services/core/my-service.ts" is not exported from "src/services/core/index.ts"
+```
+
+**Action:** Add the export to the module's `index.ts`:
+```typescript
+// src/services/core/index.ts
+export { MyClass } from './my-service';
+```
+
+### 2. Missing Main Exports
+
+**Meaning:** A top-level export (file directly in `src/`) is not exported from `src/index.ts`.
+
+**Example:**
+```
+Export "MyUtility" from "src/my-utility.ts" is not exported from "src/index.ts"
+```
+
+**Action:** Add the export to `src/index.ts`:
+```typescript
+// src/index.ts
+export { MyUtility } from './my-utility';
+```
+
+### 3. Missing Main Module Exports
+
+**Meaning:** A module's `index.ts` is not exported from the main `index.ts`.
+
+**Example:**
+```
+Module index "src/services/core/index.ts" is not exported from main index.ts
+```
+
+**Action:** Add the module export to `src/index.ts`:
+```typescript
+// src/index.ts
+export * from './services/core';
+```
+
+### 4. Files Without Module Index
+
+**Meaning:** A file has exports but there's no `index.ts` in its directory.
+
+**Example:**
+```
+File "src/services/core/my-service.ts" has exports but no module index.ts found
+```
+
+**Action:** Either:
+- Create an `index.ts` in that directory and export from it
+- Or if it's a top-level file, export it directly from `src/index.ts`
+
+## Common Patterns
+
+### Pattern 1: Star Export (Recommended for Modules)
+
+```typescript
+// src/services/core/index.ts
+export * from './my-service';
+export * from './other-service';
+```
+
+**Note:** The script may report false positives for star exports because it can't always determine what's exported. If you see an issue but know the export is via `export *`, you can safely ignore it.
+
+### Pattern 2: Named Exports (Explicit Control)
+
+```typescript
+// src/services/core/index.ts
+export { MyClass, MyFunction } from './my-service';
+export type { MyType, MyInterface } from './my-service';
+```
+
+### Pattern 3: Re-exporting from Parent Module
+
+```typescript
+// src/services/index.ts
+export * from './core';
+export * from './batch';
+
+// src/index.ts
+export * from './services'; // This re-exports everything from services/core
+```
+
+## False Positives
+
+The script may report false positives in these cases:
+
+1. **Star Exports:** If a module uses `export * from './module'`, the script may not detect all re-exports
+2. **Internal Exports:** Some exports are intentionally internal and shouldn't be in the public API
+3. **Parent Module Re-exports:** If a parent module re-exports everything, child module exports are still accessible
+
+## Best Practices
+
+1. **Use Star Exports for Modules:** `export * from './module'` keeps index files clean
+2. **Explicit Exports for Public API:** Use named exports in `src/index.ts` for important public APIs
+3. **Internal Exports:** Don't export internal utilities from `src/index.ts`
+4. **Type Exports:** Use `export type` for type-only exports to enable tree-shaking
+
+## Integration with CI/CD
+
+Add export validation to your pre-publish checks:
+
+```json
+{
+  "scripts": {
+    "prepublishOnly": "npm run validate:exports && npm run build"
+  }
+}
+```
+
+## Troubleshooting
+
+### Script reports too many false positives
+
+The script uses regex parsing which may not catch all export patterns. If you're confident an export is properly re-exported via star exports, you can safely ignore the warning.
+
+### Need to exclude internal exports
+
+Currently, the script checks all exports. If you want to exclude certain files or exports, you can modify the script to skip specific patterns.
+
+### Module is exported but script doesn't detect it
+
+Check if the module is exported via a parent module's star export. The script checks direct exports but may miss transitive exports.
+
+## Related Documentation
+
+- [SDK Architecture](../04-REFERENCE/architecture/readme.md)
+- [API Reference](../02-CORE-GUIDES/api-reference/api-reference-readme.md)
+