Default Setting in .config.user.json?

General
1

I wonder, if there's a way to define a default user setting.

E.g. a user, entering the NR instance for the first time, should get default configuration in .config.user.json. This could be a separate - manual edited (or copied) - entry containing these settings. Here's an easy example, but this could be valid for all values.

{
    "*": {
        "editor": {
            "sidebar": {
                "order": [
                    "debug",
                    "help",
                    "context",
                    "config",
                    "info",
                    "version-control"
                ]
            }
        }
    }
}

Here user "*" represents the default config. If user johndoe opens the NR instance for the first time, the "*" config is used and moved to "johndoe". Of Course, the user then can then change and expand to his/her needs.

2 Likes
2

I don't remember seeing custom settings per user session. I think this would have to be a feature.

I kind like it but at the same time I don't think it makes sense when I compare it with other editors, like vscode. There is no concept of isolated user experience in the same editor instance in vscode. Two Users connected to the same instance will have the same experience. I think that even extensions are bound to the instance not to the User.

3

What do you mean by Johndoe opening the NR instance?

4

Linting rules are unique per user. Just like it can be in vscode. Not sure about formatting, I think that's global in nr.

5

JohnDoe is just another user. It's a dummy name. :laughing:

6

Well, the individual user configs are stored in file .config.user.json. It contains one object per user, like this for user "johndoe":

{
    "johndoe": {
        "editor": {
            "view": {
                "view-store-zoom": false,
                ...
            },
            "keymap": {
	        ...
	        }
        },
        "git": {
            ...
        }
        ...
    }
}

Node-RED maintains it automatically whenever the user changes something in his/her settings. This is an easy way to handle individual configs.

However, I wonder, it there's a way to provide a default, e.g. using a user "*", or "_". This way company preferred settings could be distributed to first time users.

1 Like