Add fail mode to exit with non-zero status if no matches found #65
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.
This pull request introduces a new
failMode
feature to the CLI tool, which ensures the program exits with a specific status code if no matches are found during a replace operation. It also adjusts the exit codes for various error scenarios.Key changes include:
New Feature:
failMode
failMode
boolean flag to theCLI
struct and its associated command-line flag. (internal/cli/cli.go
) [1] [2]replaceProcess
method to return a boolean indicating whether any matches were found. (internal/cli/cli.go
) [1] [2]Run
method to check thefailMode
flag and exit with a newExitCodeNoMatch
if no matches are found. (internal/cli/cli.go
) [1] [2]Exit Code Adjustments
ExitCodeParseFlagError
andExitCodeFail
to 2, and introducedExitCodeNoMatch
with a value of 1. (internal/cli/cli.go
)Test Updates
failMode
feature and adjusted exit codes. (internal/cli/cli_test.go
) [1] [2] [3] [4] [5] [6] [7] [8]ReplaceProcess
method in the test export file to match the new signature. (internal/cli/export_test.go
)