pack folders which do not themselves contain packs are skipped in the folder hierarchy

[admiralnlson]

What happened?

Pack folders which do not themselves contain packs are skipped in the folder hierarchy introduced with feature #9033.

---

The following Manifest configuration works as expected:

  "packFolders": [
    {
      "name": "Castle Falkenstein - Lorebooks",
      "sorting": "m",
      "packs": [
        "spells-1",
        "spells-2",
        "spells-3"
      ]
    },
    {
      "name": "Castle Falkenstein - Other",
      "sorting": "m",
      "packs": [
        "abilities-corebook",
        "weapons"
      ]
    }
  ],

=> It creates 2 folders called "Castle Falkenstein - Lorebooks" and "Castle Falkenstein - Other" => OK

But this one doesn't:

  "packFolders": [
    {
      "name": "Castle Falkenstein", 
      "sorting": "m",
      "folders": [
        {
          "name": "Lorebooks",
          "sorting": "m",
          "packs": [
            "spells-1",
            "spells-2",
            "spells-3"
          ]
        },
        {
          "name": "Other",
          "sorting": "m",
          "packs": [
            "abilities-corebook",
            "weapons"
          ]
        }
      ]
    }
  ],

It creates 2 folders called "Lorebooks" and "Other" at root level, skipping the "Castle Falksenstein" intermediate parent entirely => KO.

I tried adding an explicit empty packs array (as opposed to leaving it undefined) to the parent object like so:

      "packs": [],

but the outcome is the same. The parent folder was yet again skipped.

The only way for the folder hierarchy to be generated as expected is to make sure all folders at all levels contain at least one pack, which I believe should not be a requirement.

Please allow empty folders / folder levels also.

What ways of accessing Foundry can you encounter this issue in?

• Native App (Electron)
• Chrome
• Firefox
• Safari
• Other

Reproduction Steps

see example above

What core version are you reporting this for?

11.297

Relevant log output

I don't believe there is anything about it in the console.

Bug Checklist

• The issue occurs while all Modules are disabled