-
-
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
[addonservices] Add version filtering #2811
Conversation
We need some additional decisions:
|
I think that is currently the only way to add this data. It would be nice if there was a way to add metadata to Discourse topics that can also be retrieved using the Discourse REST API. But probably @ghys already looked into this before going with this approach. 😉
I wouldn't mind having an extra "Show Incompatible Add-ons" filter option in the UI for this similar to the "Show Unpublished Entries" filter option. I'd also replace "Bundles" with "Add-ons" in the "Show Non-Stable Bundles" config option of the Json 3rd Party Add-on Service, because I think this filter is also applied to widgets/templates/block libs and KAR files? |
@@ -11,6 +11,11 @@ | |||
<description>Defines whether openHAB should access the remote repository for add-on installation.</description> | |||
<default>true</default> | |||
</parameter> | |||
<parameter name="includeIncompatible" type="boolean"> |
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.
Shall we move this file to the org.openhab.core
bundle? It affects all add-on services (remote
is used by the other add-on services, too) and is IMO placed wrong in org.openhab.core.karaf
.
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.
I see it is already used in the AbstractRemoteAddonService
so that would make sense.
It might still be nice if there was also a config option to easily disable the marketplace completely. 😉
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.
I added that option to the community marketplace. The JSON 3rd party add-on service can be easily disabled by deleting the URL.
IMO for the best user experience all of the add-on service related parameters (system:jsonaddonservice
, system:marketplace
and system:addons
) should be shown in one place in the UI.
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.
I added that option to the community marketplace.
Yes I now see the option! 🕵️
should be shown in one place in the UI
For openHAB itself that probably makes sense. But if other distros do not deploy some add-on service bundles, you'll probably end up with unused options in the UI. 🤔
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.
I would not use the same PID, the UI should just group these PIDs in one page.
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.
If it can do that it would indeed be nice. IIRC the MQTT broker config that was removed in
#2842 also had some kind of mechanism to group multiple configs. Though I don't know if it used different PIDs.
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.
I have no idea, UI is a mystery to me. Maybe @ghys can comment on that.
Anyway, I think this is out of scope here and none of the changes makes it harder to implement that later.
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
Signed-off-by: Jan N. Klug <github@klug.nrw>
9055dff
to
d9deb7e
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.
Thanks for the PR. 👍 I only have a few minor comments left!
bundles/org.openhab.core.addon.marketplace/src/main/resources/OH-INF/config/marketplace.xml
Outdated
Show resolved
Hide resolved
...b.core.addon.marketplace/src/main/java/org/openhab/core/addon/marketplace/BundleVersion.java
Outdated
Show resolved
Hide resolved
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.
Thanks for the PR. 👍 I only have a few minor comments left!
.../org/openhab/core/addon/marketplace/internal/community/CommunityMarketplaceAddonService.java
Show resolved
Hide resolved
.../org/openhab/core/addon/marketplace/internal/community/CommunityMarketplaceAddonService.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Jan N. Klug <github@klug.nrw>
I think I addressed all your comments. |
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! Let's give it a test. 🚀
For some reason if I disable "Enable Community Marketplace" it still keeps showing marketplace add-ons. |
I‘ll check that tomorrow. If they are installed, that is expected, as it would be impossible to uninstall them otherwise. |
…n options This makes it possible to use Crowdin for translating the new configuration options introduced in openhab#2811. Signed-off-by: Wouter Born <github@maindrain.net>
This pull request has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/marketplace-rules-for-3-4-0-vs-4-0-0-new-bindings/142358/3 |
With this fix it will use the correct string for pattern matching add-on version ranges introduced in openhab#2811. Signed-off-by: Wouter Born <github@maindrain.net>
* Fix Marketplace add-on range pattern matching With this fix it will use the correct string for pattern matching add-on version ranges introduced in #2811. Signed-off-by: Wouter Born <github@maindrain.net>
* Fix Marketplace add-on range pattern matching With this fix it will use the correct string for pattern matching add-on version ranges introduced in #2811. Signed-off-by: Wouter Born <github@maindrain.net>
Signed-off-by: Jan N. Klug <github@klug.nrw> GitOrigin-RevId: 4577562
* Fix Marketplace add-on range pattern matching With this fix it will use the correct string for pattern matching add-on version ranges introduced in openhab#2811. Signed-off-by: Wouter Born <github@maindrain.net> GitOrigin-RevId: 5e23b0e
Fixes #2806
This enhances the add-on services with a compatible version filter. This allows displaying only compatible versions after breaking changes in openHAB core.
Discussion partly in the linked issue. Add-on services can (optionally) provide a Maven-like version range (
[3.1.0;3.3.0.M1]
or[3.0.0;3.1.0.M4)
).Tasks: