Skip to content

fix(scaffold): replace non-existent extract step with select#814

Merged
jackwener merged 1 commit intomainfrom
fix/plugin-scaffold-extract-step
Apr 5, 2026
Merged

fix(scaffold): replace non-existent extract step with select#814
jackwener merged 1 commit intomainfrom
fix/plugin-scaffold-extract-step

Conversation

@jackwener
Copy link
Copy Markdown
Owner

Summary

  • Fix plugin-scaffold YAML template using non-existent extract pipeline step
  • Replace with select: "args" which correctly extracts the args field from fetch response
  • The extract step was never registered in the pipeline registry; select is the correct step for JSON path navigation

Context

opencli plugin create generates a sample hello.yaml that uses - extract: { type: json, selector: "$.args" }. This step doesn't exist in the pipeline registry (src/pipeline/registry.ts), so the generated command would fail at runtime.

Test plan

  • TypeScript compilation passes
  • All 7 plugin-scaffold tests pass

Part of #810 (PR C)

@jackwener jackwener merged commit d7fe7a7 into main Apr 5, 2026
11 checks passed
@jackwener jackwener deleted the fix/plugin-scaffold-extract-step branch April 5, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant