`$ZED_CUSTOM_RUBY_TEST_NAME` includes double quotes for `it` blocks

[janko]

I'm using minitest/spec syntax, and have the following task configured as per the official docs:

[
  {
    "label": "-Itest $ZED_RELATIVE_FILE -n /$ZED_CUSTOM_RUBY_TEST_NAME/",
    "command": "bundle",
    "args": [
      "exec",
      "ruby",
      "-Itest",
      "$ZED_RELATIVE_FILE",
      "-n",
      "\"$ZED_CUSTOM_RUBY_TEST_NAME\""
    ],
    "cwd": "$ZED_WORKTREE_ROOT",
    "tags": ["ruby-test"]
  }
]

However, for it "foo bar", the $ZED_CUSTOM_RUBY_TEST_NAME variable turns out to be "foo bar" instead of foo bar (resulting in /"foo bar"/). But test "foo bar" correctly resolves to foo bar, so it seems the problem is with it specifically.

[vitallium]

@janko Hi, I just want to confirm that I understand this issue correctly: instead of capturing the test name with quotes, we should capture it without them?

[janko]

Correct, the extension already does it for test. For example, it "does something" will resolve to -Itest tmp/file.rb -n /"does something"/, while test "does something" will resolve to -Itest tmp/file.rb -n /does something/ with the task above. The latter are the correct arguments.

[andyw8]

Just a heads-up: When I was looking into customs tasks a while ago, I found that Zed seemed to be caching previous versions of a task in some situations, until I restarted the editor.

[janko]

Works great, thanks! 🙏🏻

I just needed to use "\"/$ZED_CUSTOM_RUBY_TEST_NAME/\"" in the last args array item, because Zed doesn't appear to send these arguments separately, it just seems to flatten them. I initially expected I wouldn't need the extra \"...\".