Tips and Tricks

Order (parent)
├── OrderItem (child)
├── OrderPayment (child)
└── OrderShipment (child)

❌ Bad example:
"Make a user"

✅ Good example:
"Create an e-commerce User Entity.
Fields: email (unique), name, phone (nullable),
role (enum: admin, user, guest),
created date, last login"

{
  properties: [
    // 1. Primary Key
    { name: "id", ... },

    // 2. Core information
    { name: "title", ... },
    { name: "content", ... },

    // 3. Foreign keys
    { name: "user_id", ... },
    { name: "category_id", ... },

    // 4. Status/flags
    { name: "status", ... },
    { name: "is_active", ... },

    // 5. Timestamps
    { name: "created_at", ... },
    { name: "updated_at", ... },
  ]
}

❌ Bad example:
- Modify 10 Entities at once
- Migrate once a week

✅ Good example:
- Modify 1-2 Entities at a time
- Migrate multiple times a day
- Test after each migration

□ Testing complete on Development DB
□ Verification complete on Testing DB
□ Data backup complete
□ Migration Preview checked
□ Rollback plan established
□ Team notified
□ Production DB migration executed
□ Application restarted and verified

1. Define all Entities
2. [Select All] → Batch generate Model + Test
3. Add business logic to each Model

1. Add only one new Entity
2. Select and generate only that Entity
3. Start development immediately

# Backup
cp src/models/User.model.ts src/models/User.model.ts.bak

# Regenerate
[Overwrite in UI]

# Restore needed logic

git add src/models/
git commit -m "Generate models for User, Post, Comment"

// Apply commonly to all Entities

Subset A: For list
- id
- title (or name)
- 1-2 core fields
- created_at

Subset B: For detail
- All general fields
- Exclude sensitive info
- Include timestamps

Subset C: With relations
- Based on Subset B
- Add needed relations

// ❌ Excessive fields
{
  ...allFields,
  author: "User.C",  // All User relations too
  category: "Category.B",
  tags: "Tag.C",
}

// ✅ Optimized
{
  id: true,
  title: true,
  content: true,
  author: "User.A",  // Minimum info only
  category_id: true,
  created_at: true,
}

user email       → User Entity's email field
post migration   → Post-related migrations
subset A         → All Subset A's

1. Define Entity (Entity tab)
   - Quick creation with AI chat
   - Set fields and relations
   ↓
2. Define Subsets (within Entity tab)
   - Create A, B, C standard Subsets
   ↓
3. Run Migration (Migration tab)
   - Check Preview
   - Execute Development → Testing order
   ↓
4. Scaffolding (Scaffolding tab)
   - Generate Model + Test
   ↓
5. Development (code editor)
   - Add Model methods
   - Implement API endpoints
   - Write tests
   ↓
6. Register Fixtures (Fixture tab)
   - Prepare test data

1. Modify Entity (Entity tab)
   - Add/modify/delete fields
   ↓
2. Check Migration Creation (Migration tab)
   - Check auto-generated migration
   ↓
3. Review Preview
   - Confirm intended changes
   - Check data loss risk
   ↓
4. Run Migration
   - Development → Testing order
   ↓
5. Modify Model (if needed)
   - Confirm type auto-sync
   - Add logic using new fields

F12 → Network tab

- Migration execution → Check /api/migrate/run
- Entity save → Check /api/entity/save
- Check response content on error

F12 → Console tab

- Check JavaScript errors
- API response error logs
- Network request failure causes