Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539)

But It is still kinda verbose and is slightly different from subdomains' issues cuz the path could be nested. Thus I do think taking advantages of allowing overriding might solve problems better.

For example, we could define some override rules like [service workers](https://w3c.github.io/ServiceWorker/#match-service-worker-registration): the manifest from longer path (a.k.a **subManifest**) always extend the one from shorter path (a.k.a **superManifest**):

- **subManifest** inherent all members undefined from **superManifest** 
- **subManifest** override all members it defined to **superManifest** 

In this case the manifests might look like:

- Taobao PWA's manifest might use:

```
"scope":"h5.m.taobao.com/"
"start_url":"h5.m.taobao.com/"
“stay_in_app": ["http://login.taobao.com"]
"theme_color": "orange"
```

- AliTrip PWA's manifest might use:
```
"scope":"h5.m.taobao.com/trip/"
"start_url":"h5.m.taobao.com/trip/home/"
"theme_color": "blue"
```
- AliTrip "sub-app" PWA's manifest might use:
"scope":"h5.m.taobao.com/trip/sub-app*/"
"start_url":"h5.m.taobao.com/trip/sub-app*/"
```

Pretty neat right? 
And It seems accommodate most use cases related to path well ;)


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/539#issuecomment-273813800