Escape password to avoid confusing bash #20
Conversation
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
|
Hear hear! I just reported a similar issue that I believe this would resolve. Although... is this just escaping parens? Should also escape spaces... |
Author
|
Replying late here. But yeah, spaces could be escaped and is easy. However, is it common to put spaces in passwords? |
Author
|
Correction. Spaces do not seem to need escaping. |
…he db dump so that it will be able to import it. Added test for it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I happened to use a password with paranthesises in it, and it didn't play nice with bash. I first tried using single quotes for hard escaping but I got confused about where in the code I could insert that.