-
-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for automatic creation of ManagedProviders for UI components #2948
Add support for automatic creation of ManagedProviders for UI components #2948
Conversation
Signed-off-by: Jan N. Klug <github@klug.nrw>
@kaikreuzer I guess this is more in line with what we do with the other registries and does not require a component for each namespace. |
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/openhab-3-3-milestone-discussion/132715/115 |
ba2946c
to
ba3cad4
Compare
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/openhab-3-3-milestone-discussion/132715/119 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO this should be probably be merged ASAP if it effectively fixes the regressions of the incomplete refactoring that unfortunately made it to M4 and broke several important features.
...enhab.core.ui/src/main/java/org/openhab/core/ui/internal/components/UIComponentProvider.java
Outdated
Show resolved
Hide resolved
Another remark: to be complete, other objects allowing both managed and non-managed providers have a FWIW that's part of the reason there wasn't any support for non-managed Providers in the initial implementation (I'm not questioning the added value of having them): there wasn't an initial need for them since they were supposed to be managed by WYSIWYG UI editors only. I would argue it's not that urgent right now to address this because there aren't any non-managed UIComponentProviders in the official distribution yet. |
Signed-off-by: Jan N. Klug <github@klug.nrw>
3edfac0
to
a84abbe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great solution, many thanks!
I agree there's a relatively strong case for that. In M4 users can't see or save:
|
Ok, I'll suggest we test a bit tomorrow and I'll see to do a new milestone build on Saturday then. |
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/openhab-3-3-milestone-discussion/132715/121 |
…nts (openhab#2948) * Add support for automatic creation of ManagedProviders for UI components Signed-off-by: Jan N. Klug <github@klug.nrw> GitOrigin-RevId: ad3a084
Supersedes #2947
Follow-Up to #2617
See https://community.openhab.org/t/openhab-3-3-milestone-discussion/132715/98
Every registry needs a managed provider for storing configurations on server-side.
Signed-off-by: Jan N. Klug github@klug.nrw