[FEAT] Force module to render even if blank/empty

[ehawman]

Description

If a module doesn't match, it is ignored/passed. Many of the examples feature modules that are formatted to be part of the structure (in this case, the node of a tree). I would like an option to force it to render that line, even if it says something like "Unknown" or "N/A" or even "".

    {
        "type": "host",
        "key": "󰌢 PC",
        "keyColor": "green",
        "alwaysShow": true,
        "defaultValue": ""
    },

Motivation

I'm working off of examples/10.jsonc, with some stuff simply commented out.

On my local Kubuntu machine, the "host" section works (PC -> Precision 3551)

Via Tailscale SSH, fastfetch isn't able to get the "host" info, and it just doesn't render the line. I would like an option to force it to render that line, even if it says something like "Unknown" or "N/A" or even "". I apologize if this already exists. I've poked around but can't seem to find it.

This could 100% be replicated inside a command module by recreating the given module yourself, but it seems like the kind of function that all modules could benefit from.

Thanks for your consideration!

Additional context

No response

[CarterLi]

If you it would fail, why not use Custom module to print something?

[ehawman]

If you it would fail, why not use Custom module to print something?

In the case of my screenshot (modified 10.jsonc), the os, wm, and host modules are serving double-duty. They are both displaying their own contents and acting as a category header or tree node. If the value isn't there, I lose out on the key and formatting as well.

So let's explore alternatives:

Custom

    {
      "condition": {
        "!host": ""
      },
      "type": "custom",
      "key": "󰌢 PC",
      "format": "Custom Build",
      "keyColor": "green"
    },

Seems that once you set a key it can't be undone. You can set it to "", but then the module name just prints.

Command

    {
      "condition": {
        "!host": ""
      },
      "type": "command",
      "key": "󰌢 PC",
      "text": "hostname",
      "format": "Custom Build",
      "keyColor": "green"
    },

This does the job. It's functionally identical to the Custom implementation, but I don't use any commands later on that this screws up so it's fine. I do have to include a dummy command so it actually renders, which is quite janky.

I'm suggesting that a function be added to the module class which forces the module to render regardless of the value. And/or setting a default value if no other value appears.

    {
      "type": "host",
      "key": "󰌢 PC",
      "keyColor": "green",
      "defaultValue": "Custom Build"
    },

This alone would ensure that the module will render, and that you can keep the structure intact. It's simple and clean.

[CarterLi]

805e277 added a condition called succeeded. If set to false, the module will be run only if the last module failed.

{
    "host",
    {
        "type": "custom",
        "condition": {
            "succeeded": false
        },
        "key": "Host",
        "format": "DIY PC"
    }
}