Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Invoke-Interpreter/PipeScript should JSONify complex arguments #896

Closed
Tracked by #895
StartAutomating opened this issue Feb 4, 2024 · 0 comments
Closed
Tracked by #895

Invoke-Interpreter/PipeScript should JSONify complex arguments #896

StartAutomating opened this issue Feb 4, 2024 · 0 comments
Assignees
@StartAutomating
Labels
enhancement New feature or request

Comments

@StartAutomating
Copy link
Owner

StartAutomating commented Feb 4, 2024 •
edited
Loading

Since Invoke-Interpreter calls many interpreters that are not PowerShell, it would help to have a "lingua franca" to send complex objects.

Luckily, there is JSON.

If the interpreter is not a [ScriptBlock], and the argument is not a [string], it should be converted into JSON.
@StartAutomating StartAutomating mentioned this issue Feb 4, 2024
Closed
3 tasks
github-actions bot pushed a commit that referenced this issue Feb 4, 2024
feat: Invoke-Interpreter - JSONifying and unrolling arguments ( Fixes #…
eb200bc 
…896 )
@StartAutomating StartAutomating self-assigned this Feb 4, 2024
@StartAutomating StartAutomating added the enhancement New feature or request label Feb 4, 2024
StartAutomating pushed a commit that referenced this issue Feb 4, 2024
feat: Invoke-Interpreter - JSONifying and unrolling arguments ( Fixes #…
97d64aa 
…896 )

Using command directly instead of variable reference.
github-actions bot pushed a commit that referenced this issue Feb 4, 2024
feat: Invoke-Interpreter - JSONifying and unrolling arguments ( Fixes #…
155b311 
…896 )

    Using command directly instead of variable reference.
StartAutomating pushed a commit that referenced this issue Feb 4, 2024
feat: Invoke-Interpreter - JSONifying and unrolling arguments ( Fixes #…
ceeb0b2 
…896 )

Passing Converted Arguments in all Circumstances
github-actions bot pushed a commit that referenced this issue Feb 4, 2024
feat: Invoke-Interpreter - JSONifying and unrolling arguments ( Fixes #…
00c13b6 
…896 )

    Passing Converted Arguments in all Circumstances
@StartAutomating StartAutomating changed the title Invoke-Interpreter should JSONify complex arguments Invoke-Interpreter/PipeScript should JSONify complex arguments Feb 4, 2024
StartAutomating pushed a commit that referenced this issue Feb 4, 2024
fix: Invoke-PipeScript - Passing JSON arguments to interpreters ( Fixes
6bef18f 
#896 )
StartAutomating pushed a commit that referenced this issue Feb 4, 2024
fix: Invoke-PipeScript - Not using .ForFile to search languages ( Fixes
d5a019b 
#896 )

ForFile excludes template files
StartAutomating pushed a commit that referenced this issue Feb 7, 2024
feat: Invoke-Interpreter now uses Language.HasPowerShellInterpreter ( F…
c3c7498 
…ixes #904, Fixes #896 )
github-actions bot pushed a commit that referenced this issue Feb 7, 2024
feat: Invoke-Interpreter now uses Language.HasPowerShellInterpreter ( F…
e9b2ca5 
…ixes #904, Fixes #896 )
@StartAutomating StartAutomating mentioned this issue Feb 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StartAutomating StartAutomating

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@StartAutomating