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

fix git mv commands when migrating files with $ characters #6129

Merged
merged 4 commits into from
Aug 20, 2022
Merged

Conversation

Rich-Harris
Copy link
Member

This should fix #6113 — tested with the case in that issue, works fine, though I'd appreciate a sanity check from others

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

@changeset-bot
Copy link

changeset-bot bot commented Aug 20, 2022

🦋 Changeset detected

Latest commit: 4fe6202

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte-migrate Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@Rich-Harris Rich-Harris changed the title Gh 6113 fix git mv commands when migrating files with $ characters Aug 20, 2022
@@ -46,7 +47,7 @@ export function error(description, comment_id) {
*/
export function move_file(file, renamed, content, use_git) {
if (use_git) {
execSync(`git mv ${JSON.stringify(file)} ${JSON.stringify(renamed)}`);
execSync(`git mv ${sq.quote([file, renamed])}`);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we use https://nodejs.org/dist/latest/docs/api/child_process.html#child_processexecfilefile-args-options-callback instead so we can pass in an array of arguments directly and not have to worry about the shell escaping?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Untested, but I think it'd be execFileSync('git', ['mv', file, renamed]).

Copy link
Member

@dominikg dominikg Aug 20, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ohh, thats nice.
Seems to work alright for \n and $
execFileSync:

node -e 'console.log(require("child_process").execFileSync("echo",["bla\\n$1"]).toString())'
bla\n$1

execSync:

node -e 'console.log(require("child_process").execSync("echo bla\\n$1").toString())'
blan

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooh yeah that's way better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate tool passing unescaped shell commands?
3 participants