Bug report: Strange toTable behavior

[kingthorin]

Describe the bug

0. toTable in the live client implementation seems to work as expected:

1. I then tried to do the same via CyberChef-server swagger interface running in docker (per the clone, build, run instructions in the README)

{
  "input": "mess with the best, die like the rest",
  "recipe": [
    {
      "op": "toTable"
    }
  ]
}

2. Note "rest" is missing in the output 😞

3. Wondering WTF is going on I go back and insert another "rest" in the input (at this point thinking, is "rest" a reserved word or something weird like that). mess with the best, die rest like the rest which also results in a broken output:

4. It seems like each space R r is being treated as \r for some reason? But that's just my guess.

To Reproduce
As above

Expected behavior
The result should be the same as when using the live client version.

+--------------------+--------------------+
| mess with the best |  die like the rest |
+--------------------+--------------------+

or

+--------------------+-------------------------+
| mess with the best |  die rest like the rest |
+--------------------+-------------------------+

Node version:

Seems to be 17:

 docker run -it --rm --name=cyberchef-server -p 3000:3000 cyberchef-server

> cyberchef-server@1.1.0 prod
> NODE_ENV=production node index.mjs

(node:17) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:17) Warning: Accessing non-existent property 'b2u' of module exports inside circular dependency
(node:17) Warning: Accessing non-existent property 'u2b' of module exports inside circular dependency
(node:17) Warning: Accessing non-existent property 'Pair' of module exports inside circular dependency
CyberChef Server listening on port 3000!

Additional context

On the off chance that it's relevant this is on macOS Tahoe 26.2.

[kingthorin]

Update : It seems to behave as expected if I include an args object 👍

{
  "input": "mess with the best, die rest like the rest",
  "recipe": [
    {
      "op": "to table",
      "args": {
        "Cell delimiters": ",",
        "Row delimiters": "\r\n",
        "Format": "ASCII"
      }
    }
  ]
}

This seems directly tied to the presence or not of the "Row delimiters" arg. All of the following abbreviated versions still work:

Default:

{
  "input": "mess with the best, die rest like the rest",
  "recipe": [
    {
      "op": "to table",
      "args": {
        "Row delimiters": "\r\n"
      }
    }
  ]
}

No \r, only \n

{
  "input": "mess with the best, die rest like the rest",
  "recipe": [
    {
      "op": "to table",
      "args": {
        "Row delimiters": "\n"
      }
    }
  ]
}

Empty string

{
  "input": "mess with the best, die rest like the rest",
  "recipe": [
    {
      "op": "to table",
      "args": {
        "Row delimiters": ""
      }
    }
  ]
}

Only \r, no \n

{
  "input": "mess with the best, die rest like the rest",
  "recipe": [
    {
      "op": "to table",
      "args": {
        "Row delimiters": "\r"
      }
    }
  ]
}

So the problem seems to be whatever "Row delimiters" becomes if not specified. (I tried sending null but that resulted in a bad request 😉)