@payloadcms/figma 0.0.1-alpha.6 → 0.0.1-alpha.60

package/dist/constants.js

@@ -1,27 +1,80 @@
-export const FIGMA_CLIENT_IDS = {
-    production: '',
-    staging: 'wqAToBAp4UI9AZ5M6wTfT9'
-};
-export const JWKS_URI = {
-    production: 'https://static.figmacontent.com/.well_known/jwks.json',
-    staging: 'https://static.figmacontentstaging.com/.well_known/jwks.json'
+import { getEnvVarSync } from './utils/env-management.js';
+/**
+ * Environment-specific configuration for Figma integration.
+ * Selected via FIGMA_INFRA_ENV ('production' | 'staging'), defaults to 'production'.
+ */ export const ENV_CONFIG = {
+    production: {
+        apiBaseUrl: 'https://api.figma.com',
+        authorizationUrl: 'https://www.figma.com/oauth',
+        clientId: 'lelKVTAzOekFnirnlAMbuD',
+        contentApiUrl: 'https://us-east-1.cms-tenants-001-production.figmacontent.com',
+        identityMetadata: 'https://www.figma.com/.well-known/openid-configuration',
+        jwksUri: 'https://static.figmacontent.com/.well_known/jwks.json'
+    },
+    staging: {
+        apiBaseUrl: 'https://api.staging.figma.com',
+        authorizationUrl: 'https://staging.figma.com/oauth',
+        clientId: 'wqAToBAp4UI9AZ5M6wTfT9',
+        contentApiUrl: 'https://us-east-1.cms-tenants-001-staging.figmacontentstaging.com',
+        identityMetadata: 'https://staging.figma.com/.well-known/openid-configuration',
+        jwksUri: 'https://static.figmacontentstaging.com/.well_known/jwks.json'
+    }
 };
 /**
- * Get current Figma environment from environment variable
- * Defaults to 'staging' if not specified
- *
- * @returns Current environment
- */ export function getEnvironment() {
-    return process.env.FIGMA_ENV === 'production' ? 'production' : 'staging';
+ * User-facing error message when Content API returns 404 or 410.
+ * Used by the db adapter for consistent messaging at runtime.
+ */ export const CONTENT_SYSTEM_NOT_FOUND_MESSAGE = 'Content system not found. Verify your Content System ID is correct, or contact your team admin for assistance.';
+/**
+ * Build a user-facing error message for CLI commands when a project is not found (404/410).
+ * Includes infra-env context and actionable suggestions.
+ */ export function getProjectNotFoundMessage(params) {
+    const { environment, projectId } = params;
+    return [
+        `Project not found on ${environment} (ID: ${projectId}).`,
+        '',
+        'Suggestions:',
+        '  • Verify your project ID is correct',
+        "  • Ensure you're logged into the correct Figma account",
+        '  • Contact your team admin for assistance'
+    ].join('\n');
 }
+let envOverride;
 /**
- * Get JWKS URI for a given environment
- *
- * @param env - Environment (defaults to current environment)
- * @returns JWKS URI for the environment
- */ export function getJWKSUri(env) {
-    const environment = env || getEnvironment();
-    return JWKS_URI[environment];
+ * Set infrastructure environment override (used by --infra-env CLI flag)
+ * Pass undefined to clear the override
+ */ export function setInfraEnvironment(env) {
+    envOverride = env;
+}
+/**
+ * Get current Figma infrastructure environment
+ * Priority: 1) setInfraEnvironment override, 2) FIGMA_INFRA_ENV env var, 3) .env file, 4) 'production' default
+ */ /**
+ * Get the resolved EnvironmentConfig for the current infrastructure environment
+ */ export function getEnvConfig() {
+    return ENV_CONFIG[getInfraEnvironment()];
+}
+export function getInfraEnvironment() {
+    if (envOverride) {
+        return envOverride;
+    }
+    // Check process.env first (case-insensitive)
+    if (process.env.FIGMA_INFRA_ENV?.toLowerCase() === 'staging') {
+        return 'staging';
+    }
+    // Fall back to .env file in cwd (check both new and old env var names)
+    const envFileValue = getEnvVarSync(process.cwd(), 'FIGMA_INFRA_ENV') ?? getEnvVarSync(process.cwd(), 'FIGMA_ENV');
+    if (envFileValue) {
+        const env = envFileValue.toLowerCase();
+        if (env === 'staging') {
+            return 'staging';
+        }
+        if (env !== 'production') {
+            // eslint-disable-next-line no-console
+            console.warn(`Warning: Invalid FIGMA_INFRA_ENV value "${envFileValue}" in .env file. Using production.`);
+        }
+        return 'production';
+    }
+    return 'production';
 }
 
 //# sourceMappingURL=constants.js.map

package/dist/db-content-api/README.md

@@ -0,0 +1,98 @@
+# Content API Database Adapter Parity
+
+This document explains how the Content API database adapter differs from Payload today and how it will behave once alignment is complete.
+
+The Content API is an internal service built exclusively for Payload. Because of that, the adapter should match Payload by default and only diverge when there is a strong technical reason.
+
+## Where
+
+Now  
+`{ path: "slug", operator: "equals", value: "hello", type: "text" }`
+
+Future  
+`{ path: "slug", operator: "equals", value: "hello", type: "text" }`
+
+The format stays different. This allows the Content API to evolve its filter schema, for example to support composite types like Point, which are not lexicographically sortable. Semantics must remain identical to Payload.
+
+## Pagination
+
+~~Now~~  
+~~`{ limit: 10, offset: 20 }`~~
+
+✅ Partially Implemented  
+`{ limit: 10, page: 3 }`
+
+**Status:**
+
+- ✅ Content API main endpoints use `page` (matches Payload)
+
+- ⚠️ **Issue #1 (Joins):** `JoinClause` still uses `offset` instead of `page`
+  - Payload `JoinQuery`: `{ page?: number, limit?: number }`
+  - Content API `JoinClause`: `{ offset?: number, limit?: number }`
+  - **Inconsistent** with main endpoints which use `page`
+
+**Current workaround for joins:** The adapter converts `page` to `offset`:
+
+```typescript
+// Payload join query
+{ page: 2, limit: 5 }
+// Adapter converts to offset for Content API
+{ offset: 5, limit: 5 }
+```
+
+**Future:**
+
+1. Content API should support `skip` parameter for main endpoints
+2. Content API `JoinClause` should use `page` instead of `offset` (consistent with main endpoints)
+3. Content API pagination response should match Payload's flat structure
+
+### Pagination Response Structure
+
+**Payload format (flat):**
+
+```typescript
+{
+  docs: [...],
+  hasNextPage: boolean,
+  hasPrevPage: boolean,
+  limit: number,
+  nextPage: number | null,
+  page: number,
+  pagingCounter: number,
+  prevPage: number | null,
+  totalDocs: number,
+  totalPages: number
+}
+```
+
+**Content API format (nested):**
+
+```typescript
+{
+  data: [...],
+  pagination: {
+    total: number,
+    current: { limit: number, page: number },
+    next?: { limit: number, page: number },
+    prev?: { limit: number, page: number }
+  }
+}
+```
+
+**Current workaround:** The adapter transforms Content API's nested structure to Payload's flat structure using `getPaginationData()` utility.
+
+## Slugs
+
+Now  
+`{ collection: { key: "posts" } }`
+
+Future  
+`{ collection: { slug: "posts" } }`
+
+Collection identifiers will match Payload. Consumers should not be aware of internal collection IDs.
+
+## Temporary Conversions
+
+Helpers that translate Payload queries into the current Content API format are temporary and placed in the `temp-utilities` folder.
+
+They live in the `temp-utilities` folder until the Content API is fully aligned with Payload.