mirror/FileFlowsPlugins
1
0
Fork 0
mirror of https://github.com/revenz/FileFlowsPlugins.git synced 2026-01-05 23:19:32 -06:00
Code Issues Packages Projects Releases Wiki Activity

FF-1697: additional scripting languages

Browse Source
This commit is contained in:
John Andrews
2024-08-04 20:15:06 +12:00
parent a38e0a026d
commit 9ad51503b8
5 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
BasicNodes/Scripting/BatScript.cs
View File

@@ -24,11 +24,11 @@ public class BatScript : ScriptBase
/// </summary>
[Required]
[DefaultValue(@"
REM A PowerShell script can communicate with FileFlows to determine which output to call next by using exit codes.
REM Exit codes are zero-based, so:
REM Exit Code 0 corresponds to Output 1
REM Exit Code 1 corresponds to Output 2
REM Exit Code 2 corresponds to Output 3
REM A Batch script can communicate with FileFlows to determine which output to call next by using exit codes.
REM Exit codes are used to determine the output, so:
REM Exit Code 0 corresponds to Finish Flow
REM Exit Code 1 corresponds to Output 1
REM Exit Code 2 corresponds to Output 2
REM and so on. Exit codes outside the defined range will be treated as a failure output.
REM Replace {file.FullName} and {file.Orig.FullName} with actual values
@@ -43,8 +43,8 @@ REM Add your actual batch commands below
REM Example: Copy the working file to a backup location
REM copy ""%WorkingFile%"" ""C:\Backup\%~nxWorkingFile%""
REM Set the exit code to 0
EXIT /B 0
REM Set the exit code to 1
EXIT /B 1
")]
[Code(2, "bat")]
public override string Code { get; set; }

12
BasicNodes/Scripting/PowerShellScript.cs
View File

@@ -26,10 +26,10 @@ public class PowerShellScript : ScriptBase
[Required]
[DefaultValue(@"
# A PowerShell script can communicate with FileFlows to determine which output to call next by using exit codes.
# Exit codes are zero-based, so:
# Exit Code 0 corresponds to Output 1
# Exit Code 1 corresponds to Output 2
# Exit Code 2 corresponds to Output 3
# Exit codes are used to determine the output, so:
# Exit Code 0 corresponds to Finish Flow
# Exit Code 1 corresponds to Output 1
# Exit Code 2 corresponds to Output 2
# and so on. Exit codes outside the defined range will be treated as a failure output.
# Replace {file.FullName} and {file.Orig.FullName} with actual values
@@ -44,8 +44,8 @@ Write-Output ""Original file location: $OriginalFile""
# Example: Copy the working file to a backup location
# Copy-Item -Path $WorkingFile -Destination ""C:\Backup\$([System.IO.Path]::GetFileName($WorkingFile))""
# Set the exit code to 0
exit 0
# Set the exit code to 1
exit 1
")]
[Code(2, "powershell")]
public override string Code { get; set; }

12
BasicNodes/Scripting/ShellScript.cs
View File

@@ -25,10 +25,10 @@ public class ShellScript : ScriptBase
[Required]
[DefaultValue(@"
# A Shell script can communicate with FileFlows to determine which output to call next by using exit codes.
# Exit codes are zero-based, so:
# Exit Code 0 corresponds to Output 1
# Exit Code 1 corresponds to Output 2
# Exit Code 2 corresponds to Output 3
# Exit codes are used to determine the output, so:
# Exit Code 0 corresponds to Finish Flow
# Exit Code 1 corresponds to Output 1
# Exit Code 2 corresponds to Output 2
# and so on. Exit codes outside the defined range will be treated as a failure output.
# Replace {file.FullName} and {file.Orig.FullName} with actual values
@@ -43,8 +43,8 @@ echo ""Original file location: $OriginalFile""
# Example: Copy the working file to a backup location
# cp ""$WorkingFile"" ""/path/to/backup/$(basename \""$WorkingFile\"")""
# Set the exit code to 0
exit 0
# Set the exit code to 1
exit 1
")]
[Code(2, "sh")]
public override string Code { get; set; }