This is silly. Turns out setting options at a top level app
does not percolate down to sub apps (and vice versa). You
have to apply the options to ALL express apps.
This adds lots of commented out code that provides a settings panel
to add new library sources. It is incomplete as it doesn't actually
add/update the library sources on the runtime.
For 1.3, I'm focussing on allowing additional sources get added
via the settings file only. I've done enough work on the editor
side to convince myself more work is needed than I can justify
at this time on what is otherwise not going to be a widely
used feature.
When listing icons provided by a module, if there is a png and svg
with the same name, only the svg will be listed.
If a node asks for a png icon which is not known, but there is a
corresponding svg, that will be used instead.
This gets stored in localStorage of the browser which is not
ideal. This is because we load language catalogs before we
load user preferences - so if this was stored in the runtime,
the editor wouldn't know the user's preference until it was
too late to apply it.
This is likely good enough for now - may need to do something
more convoluted later on.
Significant update to the ws module to get it completely up to date.
The jump from 1.x to 6.x has required a rewrite of our WS handling. Most
specifically the means by which you can have multiple ws servers on a
single http server has completely changed; we now have to handle the
'upgrade' event on the server ourselves.
http://expressjs.com/en/api.html#app.settings.table
Allow for setting individual options on the editor express app. This app is not available through the embedded interface when using Node-RED within another application.
Update settings with editor options
Allow editor express app options to be set in settings.js
Update settings.js
formatting
Update settings.js
Co-Authored-By: TJKoury <TJKoury@gmail.com>
editorOptions -> httpServerOptions
