feat: enhance executor and resolver detail logging in CLI

[r253hmdryou]

• Added detailed change lines for created and updated executors and resolvers in the CLI output.
• Introduced new functions to format action detail lines for better readability.
• Updated the plan functions for executors, resolvers, and workflows to include detailed change information.
• Enhanced test cases to verify the inclusion of detailed schema information for TailorDB types.
• Improved the display of function registry changes with detailed lines for added and changed scripts.

default

Executors:
  + review-completed (executor, functionRegistry)
  ~ user-created (executor, functionRegistry)
Workflows:
  ~ order-processing (workflow, functionRegistry)
TailorDB resources:
  + Project (type, gqlPermission)
  ~ Customer (type)
  ~ Supplier (type)
Pipeline resolvers:
  + reviewStatus (resolver, functionRegistry)
  ~ my-resolver.triggerOrderProcessing (functionRegistry)
Auth machineUsers:
  + review-machine-user
Auth hooks:
  ~ my-auth/before-login (authHook, functionRegistry)
Auth oauth2Clients:
  + review
  ~ sample
Plan: 5 to create, 7 to update, 0 to delete, 33 unchanged
ℹ Dry run enabled. No changes applied.

detail

Executors:
  + review-completed (executor, functionRegistry)
    + description: "Emit review completion logs"
    + trigger: schedule
    + cron: "0 12 * * *"
    + operation: function
    + script -> (added)
  ~ user-created (executor, functionRegistry)
    ~ description: "Triggered when a new user is created" -> "Triggered when a new user is created by review flow"
    ~ script -> (changed)
Workflows:
  ~ order-processing (workflow, functionRegistry)
    ~ retryPolicy.maxBackoff.seconds: "30" -> "99"
    ~ retryPolicy.maxRetries: 3 -> 9
    ~ script -> (changed)
TailorDB resources:
  + Project (type, gqlPermission)
    + fields: createdAt, key, name, updatedAt
    + hooks: createdAt.create, key.create, updatedAt.update
    + permissions: create, delete, read, update
  ~ Customer (type)
    ~ hooks.fullAddress.create -> (changed)
  ~ Supplier (type)
    ~ fields.email.required: false -> true
    - fields.fax -> (removed)
Pipeline resolvers:
  + reviewStatus (resolver, functionRegistry)
    + description: "Return review status"
    + operation: query
    + output: status, reviewer
    + pipelines: body
    + script -> (added)
  ~ my-resolver.triggerOrderProcessing (functionRegistry)
    ~ script -> (changed)
Auth machineUsers:
  + review-machine-user
    + attributes.role: "STAFF"
Auth hooks:
  ~ my-auth/before-login (authHook, functionRegistry)
    ~ invoker.machineUserName: "manager-machine-user" -> "review-machine-user"
    ~ handler -> (changed)
Auth oauth2Clients:
  + review
    + description: "Review OAuth2 client"
    + grantTypes: ["authorization_code"]
    + redirectUris[0]: "https://review.example.com/callback"
  ~ sample
    + redirectUris[2]: "https://new.example.com/callback"
    ~ requireDpop: false -> true
Plan: 5 to create, 7 to update, 0 to delete, 33 unchanged

---

[changeset-bot]

⚠️ No Changeset found

Latest commit: a3c2780

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@tailor-platform/create-sdk@869

commit: a3c2780

[claude]

📖 Docs Consistency Check

✅ No inconsistencies found between documentation and implementation.

Checked areas:

• ✅ CLI flag definition (--detail-plan) in packages/sdk/src/cli/commands/apply/index.ts:18-20
• ✅ CLI documentation in packages/sdk/docs/cli/application.md:125 - Flag is properly documented with description "Show detailed planned resource changes"
• ✅ Plan output documentation in packages/sdk/docs/cli/application.md:160-169 - Accurately describes default "preview summary" behavior vs --detail-plan "detailed list" behavior
• ✅ Implementation in packages/sdk/src/cli/commands/apply/apply.ts:515-579 - Flag is passed to all plan functions (TailorDB, Auth, Executor, Resolver, Workflow, etc.)
• ✅ Change set print behavior in packages/sdk/src/cli/commands/apply/change-set.ts:60-69 - Properly shows/hides detailLines based on the detail parameter
• ✅ Detail line generation across resource types:
  • Resolvers: packages/sdk/src/cli/commands/apply/resolver.ts:589-604 (formatResolverCreateDetailLines)
  • Executors: packages/sdk/src/cli/commands/apply/executor.ts:428-433 (formatExecutorCreateDetailLines)
  • Workflows: packages/sdk/src/cli/commands/apply/workflow.ts:391,407 (uses formatPropertyDiffLines/formatAddedPropertyLines)
  • TailorDB: packages/sdk/src/cli/commands/apply/tailordb/index.ts:1055,1064 (detailLines attached)
  • Auth: packages/sdk/src/cli/commands/apply/auth.ts:1067,1073 (detailLines attached)
• ✅ Test coverage verifies detail lines are generated correctly for all resource types

Summary:

The PR introduces a --detail-plan flag that shows property-level changes for resources (e.g., changed scripts, field updates, etc.). The documentation accurately describes:

1. The flag's purpose: "Show detailed planned resource changes"
2. The default behavior: Shows a "preview summary" without details
3. The flag's effect: Shows the "detailed list of planned changes"

The implementation correctly passes the flag through all plan functions and consistently applies it when printing change sets.

---

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 5 additional findings.