Way for dynamic extensions to have settings?

[vidartf]

I know that currently the settings system in lab requires the settings schema to be available on the server in order to allow the storing of setting values via the REST API. Please consider this a request to somehow allow dynamic extensions to also store settings, ideally in such a way that they would be stored in the same location regardless of whether it is loaded dynamically or regularly.

My apologies if this is already possible and I just missed it :)

[krassowski]

Currently the settings are stored and provided by the server. The JupyterLab API assumes server is the only source of settings in its fetch and list methods. We would either need to:

1. make a dynamic extensions a special case and change the upstream implementation of fetch, list and save (e.g. adding a client-side registry which would store the settings of dynamic extensions in the browser storage), or
2. put schema files on the server when we load dynamic extensions, ideally in a subdirectory to avoid interfering with the normal schema; each re-loading of the extension would overwrite the schema on the server

Because schema is now preferred way do define menus, toolbars etc, we really want to enable schema to have a full feature parity with the normal extensions.

I lean towards the second option.