-
-
Notifications
You must be signed in to change notification settings - Fork 26
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 categories #37
Comments
After investigating how Synology handles package categories, it appears that the category tag is linked to the JSON result from the Package Center server rather than being part of the package itself (i.e., it's not present in the package's INFO file). If we want to implement this feature, we would need to set up various categories on the server's database. Then, in the admin interface, we could enable the tagging of one or more category identifiers at the package level. This would allow the JSON result returned to clients to include this data. Should we still explore this approach? Have we seen any examples from other third-party package providers using categories? I’m curious if the Package Center displays categories for third-party packages the same way it does for Synology’s own packages. EDIT: For reference (using this #63 (comment)), Synology’s category tags in their JSON format look like this: |
@mreid-tt if we investigate into categories, we should first validate whether categories work for thirdparty packages in the DSM Package Center. |
I completely agree. No point in extending our database if DSM does not display categories for community packages. |
Package Center now displays Synology packages organized as "Categories".
It may be useful to publish SynoCommunity the same way.
The text was updated successfully, but these errors were encountered: