Bundles don't have categories
Bug #1979343 reported by
Francisco Jimenez Cabrera
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snap Store Server |
Triaged
|
High
|
Unassigned | ||
Bug Description
Hello,
On the charmhub.io website, we need to allow users to filter charms or bundles by category. We recently discovered that bundles come from the API without any defined category.
This is essential for us because we had people telling us that bundles are not visible enough on Charmhub, and this is part of the issue because as soon as someone filters by one category, all the bundles will be filtered out.
It looks like there are 24 bundles on the storefront right now, this is an example bundle without category:
https:/
Thank you!
Revision history for this message
| Daniel Manrique (roadmr) wrote | #1 |
| tags: | added: charmhub |
| Changed in snapstore-server: | |
| status: | New → Triaged |
| importance: | Undecided → High |
To post a comment you must log in.
We can manually categorize bundles in the section_ops repo.
User-set category information might come from metadata.yaml, which poses a problem because bundles don't have a metadata file.
Even if they did, we need to check with the Juju team to ensure there's a specification for category information and a field; old charms used to have "tags" which are mapped to categories, but I would need to check on our side to see whether we still do the mapping for newly-uploaded charms (I think that's not the case).
1- Check whether tag information is extracted and mapped for categories for new charms
2- Check whether we extract native category information in new charms.
3- If we do, we might simply add category support to bundle.yaml, though we need to check with the Juju team.