Issue #4185
Updated by dalley almost 6 years ago
The detail view of a repository version provides a "content summary". This looks like the following: <pre> "content_summary": content_summary = { "package": 50, "update": 2, "file": 5 } </pre> The problem is that these names come from the TYPE field on the models, and aren't namespaced by plugin. "package" comes from the RPM plugin, but that name is super generic. If another plugin (hypothetically, let's say the Python plugin", defined a content type named "package", the RPM "package"s and the Python "package"s would be counted together as if they were the same content type. A solution might be to namespace "type" by plugin somehow like so: <pre> "content_summary": content_summary = { "pulp_rpm.package": 50, "pulp_rpm.update": 2, "pulp_file.file": 5 } </pre> I would discourage a convention-based solution to this problem since with enough plugins, this will eventually become a problem. I would say it's already a problem for understandability if not correctness.