[manifest] Handleing capabilities with Manifoldjs (#412)

I want to put something out there for feed back from this community.  Manifoldjs is trying to figure out how to manage it's capabilities.  Specifically, we are allowing users to add in cordova plugins to make those APIs available in the platforms that support.  We have two options, via the command line or via the manifest.  The manifest would be prefixed of course, much like our whitelist management is:
````
"mjs_cordova": {
"pluginMode": "server",
"baseUrl": "/js/cordova",
"match": ["http://shiftr.azurewebsites.net/profile", "http://shiftr.azurewebsites.net/users/*"]
}
````
We may collapse this with the current whitelist value, since we already manage scope (and security for windows): 
````
  "mjs_access_whitelist": [
      {
          "url": "https://bancocontoso.azurewebsites.net", "apiAccess":"all"
      }
  ]
````
*Q1:  Does anyone predict capabilities needs within the manifest directly that we can align to?*

Next, we are considering enabling developers to be able to add js files to a page via the manifest, that wouldn't be added to the page when it's not an app.  This makes it easier to add js that consumes app only APIs.  It would look something like this:
````
"mjs_custom_scripts": [
    {
      "source": "js/barcode-scanner.js"
    },
    {
      "source": "http://mydomain.com/js/photo-capture.js",
      "match": ["/pictures/*", "/user/profile"],
      "platform": ["android", "ios"]
    }
  ]
````
*Q2:  Is this opening Pandora's box?  It's a big ask from developers, but I don't know if it will lead to bad habits in the future.*

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/412