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

Issue 800935 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 2
Type: Bug



Sign in to add a comment

Remove wildcards from manifests

Project Member Reported by dcheng@chromium.org, Jan 10 2018

Issue description

It means that things will have to be explicitly listed, but that will be useful for understanding what's actually exposed. Right now, "*" can be used for the service, capability, or interface, and the full set of what's exposed is not necessarily obvious. It also makes mojo manifest visualization more painful.
 

Comment 1 by dcheng@chromium.org, Jan 10 2018

Cc: roc...@chromium.org
Owner: dcheng@chromium.org
(I'll assign this to myself for now actually, I don't think anyone from Mojo core needs to work on this directly)

Comment 2 by roc...@chromium.org, Jan 10 2018

There is a decent use case for wildcards and I think we should be mindful
of it.

Consider building something like a UI shell with a launcher that wants to
tell any service "please launch with some default UI". That was the
original intent behind the "app" capability (which of course was grossly
overused and abused).

Maybe we could allow wildcard requirements iff an additional service
manager capability is explicitly required by the service?

In any case we can definitely get rid of 99% of all wildcard uses today.
Labels: ServiceManagerImprovification
Will need to give more consideration to wildcards, how they're used, and whether or not there's a better way to support such cases.
Cc: -roc...@chromium.org rockot@google.com

Sign in to add a comment