Closed SBorg2014 closed 2 years ago
@jwiesel Any idea? I think you did latest changes in config stuff? Maybe you arefaster then me to look into it :-)
Hi @SBorg2014 , @Apollon77 , I just checked, what happened.
I see two options, how to change the behavior
I am open either way. :-)
WHat about adding a second field and have it separated but add faillbacks in Admin-UI JS and main.js - if new field is null or any "default" value and the httpRoot is set to set both to the same value ... Then we achieve basically "backward compatibility" but have both fields separated configurable?
I hope i got the topic right ;-)
@jwiesel Hmm, i think option "1" is more like an Q&D? No one realy knows how long it does work.
I prefer Option "2".
A major version change of the adapter from V2.x to V3.x brings a breaking change with it. The default could be /
, that doesn't bother the user who hasn't set a path before. Users like me then have to adjust the path again ;)
@Apollon77 Then i'm out ^^
Hi @SBorg2014 , @Apollon77 , I just created PR #292 to add the requested functionality. Feel free to test and provide feedback via the URL provided in the PR.
What should i say? Great job 👍 Works perfect, thank you, merci, danke 😎
If you enter a path in the root path, it will not be used. For example
/node-red
, then the dashboard is not as expected under/node-red/ui
but only under/ui
.