feat: allow to capture command output to variable#12
Merged
MarcScheib merged 1 commit intoCycriLabs:developfrom Aug 15, 2025
Merged
feat: allow to capture command output to variable#12MarcScheib merged 1 commit intoCycriLabs:developfrom
MarcScheib merged 1 commit intoCycriLabs:developfrom
Conversation
Contributor
|
Tested locally with an example use-case. Works really nice. |
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
So far it's a bit cumbersome if you want to capture the command output to a variable. The obvious work-around being redirecting stdout to a well-known temporary file, then using
FORMULAtype step in combination withinputFileand issue another command to delete the temporary file.What is the new behavior?
You can specify
resultVariableprop on theCOMMANDtype step, this will run the command with output capturing.A subsequent
FORMULAtype step can the process the result further, e.g. split by newlines etc. to prepare entities for a select prompt etc.ppDoes this PR introduce a breaking change?
Other information