Example
I want to write a module and make it available for download, so that everyone can use it.
But in the code there are several web requests that I would like to hide, because they contain personal data.
You could add a command to which you can attach other commands and set a password on it. You can open the module in the editor and use it in your own projects, edit it, except for protected commands.
Someone can write modules for their own APIs and hide part of the module with algorithms for checking answers or generating keys.
Someone can hide part of the paid or free module. The module can be downloaded and used in the runner, but to get full access to the source code, you need to buy it.
The password on the commands does not block the launch of the module, but does not allow you to view hidden commands without a password in the editor.
Something like this.
You can set a password for the module, but it is identical for opening in the editor and in the runner.
