Repository navigation
Make the Modbus Control listing findable by keyword - #6
Merged
Merged
Conversation
The listing had none, so marketplace search matched only its name and description, and the Zelos AI saw no terms such as "registers" or "coils" for it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The listing had no keywords or categories. Marketplace search matched only its name and description. Zelos AI, which now reads every listing to pick an extension for a job, saw no terms such as "registers" or "coils" for it.
Fix. Add keywords and categories to
extension.toml.Numbers
Size
2 added lines in
extension.toml. No code changes.Commits
1. Add keywords and categories to the listing.
Behavior changes for review
modbus,modbus-tcp,modbus-rtu,registers,coils,plc,scada,industrial,automation.Rollout
The listing changes only after a release (version bump and tag). Part of the extension-discovery work in zeloscloud/src#1583.
Testing
parseManifestaccepts the new manifest.zelos extensions package .needs a builtdist/, which a fresh clone lacks, so it was not run.