`tolgee pull` CLI command with `JSON_TOLGEE` setup gives nested format rather than flattned key/value

[schang124]

I want my pulled i18n json files to have flatten key/value pair, but when I pull it from the cloud, it returns nested key.
Could you investigate this issue and give an option to have flatten key?

Here is my settings:

// package.json
"tolgee:pull": "pnpm tolgee pull"

// .tolgeerc
{
  "$schema": "https://docs.tolgee.io/cli-schema.json",
  "projectId": 12745,
  "format": "JSON_TOLGEE",
  "patterns": [
    "./src/**/*.ts?(x)"
  ],
  "push": {
    "files": [
      {
        "path": "./src/i18n/en.json",
        "language": "en"
      },
      {
        "path": "./src/i18n/ko.json",
        "language": "ko"
      }
    ],
    "forceMode": "OVERRIDE"
  },
  "pull": {
    "path": "./src/i18n"
  }
}

Results

// expected
{
  "a.b.c": "test text"
}

// actual result
{
  "a": {
    "b": {
      "c": "test text"
    }
  }
}

[cyyynthia]

I recon this is an artifact from back when Tolgee was using nested keys as the default; the CLI still requests the JSON to be structured by default. You can solve this by setting pull.delimiter to null.

[schang124]

I recon this is an artifact from back when Tolgee was using nested keys as the default; the CLI still requests the JSON to be structured by default. You can solve this by setting pull.delimiter to null.

Thank you! The solution worked and I also found the document has the information.

It is my fault not going through all the options on the document, but it would be helpful if you specify it on .tolgeerc example configuration which many people follow, copy and paste.

[JanCizmar]

I believe you wanted to say pull.delimiter, but anyway. I think that we should be aligned with the the UI, where by default JSON_TOLGEE is flat.

@stepan662 I thought that it works the same also in the cli. 🤔 Am I wrong?

[stepan662]

I'm not sure if it's a bug or a feature. I would be for making a small breaking change and having it flat by default. As this is a common complaint.