Mixed configuration property or optional?

FezVrasta · 30 August 2023 11:57

Hi, I need to allow my node to accept one configuration node, but I want it to be one of many types.

I have matter-server and matter-aggregator and I would like the server property of my node to accept one from either lists. Is this possible?

If not, I would have to display two separate dropdowns and have the user pick from just one of them, but if I do that, Node-RED forces the user to select an option from each of the dropdowns even though I marked them as optional, ideas?

I guess if the above is not possible I will have to create my custom-made type dropdown, it's not a big deal but I would really like to do it only if there's not a better Node-RED standard way

knolleary · 30 August 2023 12:46

Hi @FezVrasta

it isn't possible to have a single property to be selected from multiple types - you will need to have two separate properties.

It is possible to mark an config property as optional. For example, the HTTP Request node has an optional TLS config node property:

github.com

node-red/node-red/blob/master/packages/node_modules/@node-red/nodes/core/network/21-httprequest.html#L230


      
                  value:"",
                  validate: function(v, opt) {
                      if ((v.trim().length === 0) ||
                          (v.indexOf("://") === -1) ||
                          (v.trim().indexOf("http") === 0)) {
                          return true;
                      }
                      return RED._("node-red:httpin.errors.invalid-url");
                  }
              },
              tls: {type:"tls-config",required: false,
                    label:RED._("node-red:httpin.tls-config") },
              persist: {value:false},
              proxy: {type:"http proxy",required: false,
                      label:RED._("node-red:httpin.proxy-config") },
              insecureHTTPParser: {value: false},
              authType: {value: ""},
              senderr: {value: false},
              headers: { value: [] }
          },
          credentials: {

FezVrasta · 30 August 2023 14:44

Thanks, I managed to make the optional property working, I'm not really sure why it kept complaining initially.

system · 13 September 2023 14:44

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Multiple and dynamic configuration nodes Developing Nodes	0	883	24 January 2020
Event when config node is selected General	0	314	24 June 2019
Editor select options from server side data Developing Nodes	4	382	5 April 2021
Can't we create a custom node with more than one inputs General	3	1297	3 August 2018
Enhancement request: enable config-nodes to accept msg variables to set config at runtime Core Development typedinput	2	164	9 May 2023

Mixed configuration property or optional?

Related Topics