fix: replace nonexistent extract step in plugin scaffold#812
Closed
fix: replace nonexistent extract step in plugin scaffold#812
Conversation
…gin scaffold The YAML template generated by `opencli plugin create` used an `extract` step that doesn't exist in the pipeline registry, causing runtime errors. Replace with `select` which handles JSONPath selection correctly. Closes part of #810
Owner
Author
|
Closing in favor of opus0's #814 (same fix, both approved) |
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
1 participant
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 step which doesn't exist in the registryselect(JSONPath selection), which is the correct step for this operationUnknown pipeline step "extract"error when running scaffolded pluginsPart of #810
Test plan
opencli plugin create test-plugingenerates valid YAMLhellocommand works end-to-end