New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 669068 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Nov 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Make it easy for groups of interfaces to include other groups

Project Member Reported by sky@chromium.org, Nov 28 2016

Issue description

The UI service has (at least) two unique sets of clients ( https://chromium.googlesource.com/chromium/src/+/master/services/ui/manifest.json ) . There is the typical client, 'app', and the 'window_manager'. Both of these classes have a core set that is the same, and then a couple of unique interfaces. Currently this is done by duplicating the interfaces between the two classes. It would be nice if there was a way to define a group that the other two groups referred to, e.g.:

common: [ the common interfaces ]
app: [common, app-specific interfaces]
window_manager: [common, wm-specific interfaces]
 
Cc: -roc...@chromium.org rockot@google.com
Status: Fixed (was: Untriaged)
I don't think this is still relevant since manifests can always provide multiple capability classes, and other services can require multiple from that service. I don't really recall what things were like when this was filed. Please re-open if I'm misinterpreting the bug.

Sign in to add a comment