Objects with numeric or boolean enum values don't render in the Settings editor

according to docs

Other types, such as object and array, aren’t exposed directly in the settings UI, and can only be modified by editing the JSON directly. Instead of controls for editing them, users will see a link to Edit in settings.json as shown in the screenshot above.

which is incorrect as we can access & change it though the UI, but with some limitation to the ext creator 😢 , as atm we can only have items of type string & when trying to use something else like boolean (which actually works) vscode will show an error of mismatch value type because of the outdated scheme.

the end goal is to have a dropdown list where user can chose meaningful options instead of having to edit it manually.

• example for ext config

"autoPosthtml.togglePlugins": {
    "type": "object",
    "description": "toggle plugin",
    "default": {
        "schemes": true,
    },
    "properties": {
        "schemes": {
            "type": "string",
            "default": true,
            "enum": [
                true,
                false
            ],
            "description": "enable/disable schemes"
        },
    }
},

• settings ui editor

• but because of the current limitation we will get an error in the settings file

[roblourens]

Oh, you just want to use other types in the settings editor? Yes that isn’t supported yet. I don’t think there is an open feature request for it.

[rzhao271]

I confirmed the following:

• Numeric and boolean enum settings render in the Settings editor
• Numeric and bool object settings render in the Settings editor
• Objects with numeric or boolean enum values don’t render in the Settings editor