decoupled-cli 2.3.2 → 2.4.1

package/examples/.cursorrules

@@ -1,189 +0,0 @@
-You are the Cursor AI working in a Next.js + Drupal monorepo. Follow these rules to deliver complete, working features end-to-end.
-
-# Project Overview
-- Architecture: Headless Drupal backend with Next.js frontend
-- Backend: Drupal 11 with GraphQL Compose and DC Import API
-- Frontend: Next.js 15 with TypeScript, Tailwind CSS, Apollo GraphQL
-- Environment: DDEV local development
-
-# Environment Configuration
-- Environment variables in `.env.local`:
-  - `NEXT_PUBLIC_DRUPAL_BASE_URL` – Drupal base URL
-  - `DRUPAL_CLIENT_ID` / `DRUPAL_CLIENT_SECRET` – OAuth credentials
-  - `DRUPAL_REVALIDATE_SECRET` – On-demand revalidation secret
-  - `NODE_TLS_REJECT_UNAUTHORIZED=0` – Allow self-signed certs (dev)
-
-# DC CLI Usage
-**CRITICAL**: Use DC CLI instead of direct API calls.
-
-First-time setup:
-```bash
-decoupled-cli auth login         # Authenticate with platform
-decoupled-cli spaces use <id>    # Set default space (optional)
-decoupled-cli spaces current     # Verify setup
-```
-
-# End-to-End Workflow
-When asked to implement a new content type (e.g., “create a product page”), complete all steps:
-
-1) Verify CLI authentication
-```bash
-decoupled-cli auth status        # Check if authenticated
-decoupled-cli spaces list        # List available spaces
-decoupled-cli spaces use <id>    # Set default space if needed
-```
-
-2) Plan content type
-- Define name + machine name
-- List fields and types
-- Determine components, routes, display needs
-
-3) Create DC Import JSON
-- Get example format: `decoupled-cli spaces content-import --example`
-- Include model definition and sample content
-- Important: In `values`, use field ID directly, never with `field_` prefix
-- For image fields: Use full URLs with Drupal domain from `.env.local`, not relative paths
-
-Template:
-```json
-{
-  "model": [
-    {
-      "bundle": "content_type_name",
-      "description": "Description",
-      "label": "Content Type Label",
-      "body": true,
-      "fields": [
-        { "id": "field_name", "label": "Field Label", "type": "text|string|image|datetime|bool|text[]" }
-      ]
-    }
-  ],
-  "content": [
-    {
-      "id": "item1",
-      "type": "node.content_type_name",
-      "path": "/content-type/item-slug",
-      "values": {
-        "title": "Item Title",
-        "body": "<p>Body content</p>",
-        "field_name": "field_value",
-        "image_field": {
-          "uri": "${DRUPAL_BASE_URL}/modules/custom/dc_import/resources/placeholder.png",
-          "alt": "Image description",
-          "title": "Image title"
-        }
-      }
-    }
-  ]
-}
-```
-
-4) Import via DC CLI
-```bash
-# Import content type and sample content
-decoupled-cli spaces content-import --file content-type-import.json --preview  # Preview first
-decoupled-cli spaces content-import --file content-type-import.json              # Apply changes
-
-# Generate example if needed
-decoupled-cli spaces content-import --example > content-type-import.json
-```
-- **CRITICAL**: Immediately run schema generation:
-```bash
-npm run generate-schema
-```
-- Verify: machine names, created nodes, and GraphQL schema updates
-
-4) Implement frontend
-- Files:
-```
-app/
-  components/
-    [ContentType]Card.tsx
-    [ContentType]Renderer.tsx
-    DynamicIcon.tsx (optional)
-  [content-type]/page.tsx
-  [...slug]/page.tsx (update)
-lib/
-  queries.ts (update)
-  types.ts (update)
-```
- - GraphQL: add list query and update `GET_NODE_BY_PATH` cases
- - Types: add `Drupal[ContentType]` and `[...]Data` interfaces
- - Components: card + renderer; use `dangerouslySetInnerHTML` for processed HTML
- - Routing: handle in dynamic route switch by `__typename`
- - Navigation: add link in `app/components/Header.tsx`; update `navigationItems` and active detection with `pathname.startsWith('/route/')`
- - DC GraphQL fields return simple types (`string`, `string[]`, `bool`, etc.), not `{ processed }` objects — probe schema with a quick query before typing components
-
-5) Build and test
-- `npm run build` → fix TypeScript/build errors
-- `npm run dev` → verify listing and detail views
-- Check URLs: `/[content-type]`, `/[content-type]/[slug]`
-
-Checklist:
-- [ ] DC import succeeds
-- [ ] **Schema generation runs (`npm run generate-schema`)**
-- [ ] GraphQL schema exposes fields
-- [ ] Types compile
-- [ ] Build passes
-- [ ] Listing and detail pages render
-- [ ] Navigation works, responsive design verified
-
-# Component Architecture
-- Per type, create `[ContentType]Card.tsx` (listing) and `[ContentType]Renderer.tsx` (detail)
-- Cards: preview data + CTA; Renderers: full display, responsive layout
-- Place components in `app/components/`; listing in `app/[content-type]/page.tsx`; update `app/[...slug]/page.tsx` to route by `__typename`
-
-# Field Types Reference
-- `text` – Rich HTML field
-- `string` – Short text (≤255 chars)
-- `image` – Single image upload
-- `image[]` – Multiple image uploads
-- `datetime` – Date/time
-- `bool` – Boolean
-- `text[]` – Rich HTML list
-- `string[]` – Plain text list (recommended for features/specs)
-
-# Common Patterns
-- Product: `price (string)`, `product_images (image[])`, `in_stock (bool)`, `features (string[])`
-  - Image URI: `{"uri": "${DRUPAL_BASE_URL}/modules/custom/dc_import/resources/placeholder.png", "alt": "Product image", "title": "Product"}`
-- Event: `event_date (datetime)`, `location (string)`, `speakers (string[])`
-- Team: `position (string)`, `profile_image (image)`, `bio (text)`
-  - Image URI: `{"uri": "${DRUPAL_BASE_URL}/modules/custom/dc_import/resources/placeholder.png", "alt": "Team member photo", "title": "Profile"}`
-- Case Study: `project_url (string)`, `technologies (string[])`, `project_images (image[])`
-  - Image URI: `{"uri": "${DRUPAL_BASE_URL}/modules/custom/dc_import/resources/placeholder.png", "alt": "Project screenshot", "title": "Interface"}`
-
-# Troubleshooting
-- DC import fails: check OAuth, JSON structure, no `field_` in values
-- **Schema not updated**: ALWAYS run `npm run generate-schema` after DC imports
-- GraphQL errors: confirm content type exists, clear GraphQL cache, regenerate schema
-- Build errors: verify types, imports, query syntax
-- Content not showing: confirm field names match GraphQL schema; for HTML use `dangerouslySetInnerHTML={{ __html: field.processed }}`
-- **Field name mismatches**: DC field IDs may transform (e.g., `in_stock` → `inStock` in GraphQL)
-
-Debug commands:
-```bash
-decoupled-cli auth status                                          # Check authentication
-decoupled-cli spaces list                                          # List available spaces
-decoupled-cli spaces current                                       # Show default space
-decoupled-cli health check                                         # Platform status
-decoupled-cli spaces content-import --file test.json --preview    # Preview import
-# MOST IMPORTANT: Generate fresh schema after any import
-npm run generate-schema
-# Check schema includes your content type
-grep -i [content_type] schema/schema.graphql
-```
-```
-
-# Best Practices
-1. **ALWAYS run `npm run generate-schema` immediately after DC imports**
-2. Create sample content for immediate testing
-3. Prefer `string[]` for simple lists; use `text[]` only when necessary
-4. Verify GraphQL field names against the actual schema (may differ from DC field IDs)
-5. Handle empty/missing data gracefully
-6. Keep TypeScript types accurate and complete
-7. Use semantic HTML and ensure responsive design
-8. **Navigation integration**: Update `navigationItems` array and use `.startsWith()` for active detection
-9. **Component architecture**: Create Card + Renderer components per content type
-
-# Success Criteria
-- Builds without errors; routes render correctly; navigation works; responsive; proper fallbacks; follows design patterns; integrates with existing auth and routing.