Gracefully handle non existend receive config file #685
Conversation
This file contains 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
If croc shall not remember the config, it should not exit if the config file could not be opened. This is similar to the handling of the send config.
|
thanks, this looks great! |
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.
This PR is based on #684
As I understand the handling of
send.jsonin thesendfunction, it prints but ignores an error ofutils.GetConfigDir(). I tried to copy this behavior to thereceivefunction:If
utils.GetConfigDir()fails, the error is printed and returned toreceive. Though, croc only exits ifc.Bool("remember")istrue, because only then, the config file is really needed.This may be related to #681