[BUG] Custom object inherits key from previous custom object if key is blank

[nickgerace]

General description of bug:

• What happened: if you create a second "custom" object and leave the key blank, it will inherit the last "custom" key
• What should happen: the second "custom" object's key should be blank
• Fastfetch version used: 2.33.0
• Did it work in an older version: unknown
• Where did you get the binary: nixpkgs
• Does this issue still occur in the latest dev build?: unknown

Often helpful information:

Configuration file:

{
  "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
  "display": {
    "size": {
      "ndigits": 0
    }
  },
  "modules": [
    {
      "type": "custom",
      "key": "My Key Here",
      "format": "Some text",
    },
    {
      "type": "custom",
      "format": "―――――――――――――――――――――――"
    },
  ]
}

Bad output:

My Key Here: Some text
My Key Here: ―――――――――――――――――――――――

Expected output:

My Key Here: Some text
―――――――――――――――――――――――

If fastfatch crashed or froze

n/a

If fastfetch is slow

n/a

If an image or logo didn't show

n/a

If fastfetch behaves incorrectly on shell startup

n/a

[CarterLi]

You can set the key to a white space, which is used as a special value for removing keys.

    {
      "key": " ",
      "type": "custom",
      "format": "―――――――――――――――――――――――"
    },

[nickgerace]

Thank you! That worked as a workaround.

I still believe this is a bug, but I appreciate the workaround.

[CarterLi]

FYI this issue affects not only key of custom, but also all other modules and properties, as it was designed like that (counter-intuitive though). However, we won't change current behavior before removing support of module specific command flags, probably.

[nickgerace]

Ah that makes sense. Okay that sounds good.