Thank you for that fast clarification. That leaves me with 1 final question when it comes to utilizing the setting. I see that it is easily accessible in the node's settings editor as RED.settings.myNodeSomeSetting. I am missing the docs showing how to access it on the backend. Can you enlighten me, please? Thanks for the tutelage.
Thanks. That was the first thing I tried and get undefined each time. I must be doing something wrong. I though maybe there was a getter method on the settings object that I was failing to find.
p.s. I am pretty sure I am atleast setting it correctly, because I can see the value in oneditprepare .
All of the settings can be set by the user via their settings.js file. The exportable flag determines whether that setting is exposed in the editor as well as the runtime.
But the value should be considered read-only.
If you have set exportable to true, then yes, you can access the value in the edit dialog of your node. But you cannot change its value from there.
Ok. I think I misunderstood the api. If I want the setting available in my backend node constructor as RED.settings.myNodeMySetting, then it must be defined in the settings.js or it will be undefined. If I want to make it available to the settings page, then I have to also add it when using registerType. I thought that the backend could access the default value set during registerType. Sorry for the confusion.
What I have gathered is that I can check if the setting is defined from settings.js before registerType is called. I can update the value and make it visibile in the settings dialog page as informational showing the user which lib is being used along with instructions to edit it in settings.js and reboot the server.