Allow an app to register as a handler for all content types
Bug #1430073 reported by
Robert Schroll
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| content-hub (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Currently, the only way for an app like the file manager to register as a handler for all types of content is to list each content type in its JSON configuration file. Each time a content type is added, such apps need to add that type to their configuration. Instead, apps that anticipate being able to handle all content types should be able to list "all" in their configuration files, much like they can use ContentType.All in QML.
| tags: | added: convergence |
| Changed in content-hub: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| affects: | content-hub → content-hub (Ubuntu) |
To post a comment you must log in.
