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.

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

Introducing flag to unescape subst string #42

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

assarbad
Copy link

  • This introduces the -S / --subst-escapes flag which will unescape the substitution string prior to performing the substitution.
  • Allows to work without the help of a shell or with shells incapable of passing substitution string arguments with certain special characters.
  • Special characters implemented are \t, \n, \r, '\ ' (blank space), \", \$, \', \\, \`
  • Added test cases for the newly added code.
  • Bumped the version number in Cargo.toml

It's a new flag so as not to break backwards compatibility.

If merged, this addresses #13 and #31.

If any changes are required, please advise and I will resubmit by force-pushing another signed commit.

@facebook-github-bot
Copy link
Contributor

Hi @assarbad!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@assarbad
Copy link
Author

Signed the CLA.

@assarbad assarbad force-pushed the escape-substitution-string branch from fc4d4f5 to 9294bb1 Compare February 28, 2023 23:01
@assarbad
Copy link
Author

Sorry, had forgotten to run cargo fmt on the code. This was done with the latest change.

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Feb 28, 2023
@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-bot
Copy link
Contributor

@swolchok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@swolchok
Copy link
Contributor

@swolchok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

the import failed due to conflicts

- This introduces the -S / --subst-escapes flag which will unescape the
substitution string prior to performing the substitution.
- Allows to work without the help of a shell or with shells incapable of
passing substitution string arguments with certain special characters.
- Special characters implemented are \t, \n, \r, '\ ' (blank space), \",
\$, \', \\, \`
- Added test cases for the newly added code.
- Bumped the version number in Cargo.toml
- Ran 'cargo fmt' on the code
@assarbad assarbad force-pushed the escape-substitution-string branch from 9294bb1 to d3270fe Compare April 23, 2024 20:15
@assarbad
Copy link
Author

@swolchok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

the import failed due to conflicts

@swolchok Yep, maybe you can hold it for a bit. I'd like to address whatever review comments you say you had, then recommit (i.e. amend). Alas, they're not visible to me (see also other comment on #13 ... may take a few more minutes to finish).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Do not delete this pull request or issue due to inactivity.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants