fix(scaffold): replace non-existent extract step with select#814
Merged
fix(scaffold): replace non-existent extract step with select#814
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
extractpipeline stepselect: "args"which correctly extracts theargsfield from fetch responseextractstep was never registered in the pipeline registry;selectis the correct step for JSON path navigationContext
opencli plugin creategenerates a samplehello.yamlthat 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
Part of #810 (PR C)