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.
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 registry metadata to published components. #132
Add registry metadata to published components. #132
Changes from all commits
0d4f67c
d88e406
9b5e26b
7e3cb0a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Are
keywords
distinct fromcategories
? They seem coupled in the original registry discussion.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.
crates.io
has them as distinct fields, where keywords is for describing the package and the category with a set of predefined slugs to use.I wasn't following the discussion around the metadata implementation closely, so it sounds like we should be populating this off of
keywords
instead of categories or perhaps both?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.
Ah! Given what you linked, i think distinct fields make the most sense (and AFAICT upon closer look seems to be what the registry discussion proposes). cc/ @Kylebrown9 to check my interpretation.
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'm going to switch to populating the
categories
field from the cargokeywords
as I believe that's more of the intention of this field in the registry metadata; the predefined categories list from cargo doesn't map to what we'd want in a component registry anyway.I've opened bytecodealliance/registry#197 to track the confusion here.
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've decided to merge this as-is and wait for the resolution on the linked issue; will update
cargo-component
if things change.