Load app builder CLI parameters via manifest.json and CSP headers

[daniellacosse]

PWAs are often configured by a manifest.json served from the same origin - we can pull this down and parse it to infer app name and icon information! CSP headers often contain additional domains as well!

[marceloomens]

@daniellacosse can you give me some insight on how the web wrapper app template using both the entryUrl and entryDomain replacement values, where they are used in the app template, and how they are used differently?

I'm pulling the start_url value from manifest.json, and I'm curious how this value best maps onto either entryUrl or entryDomain or both.

[daniellacosse]

@daniellacosse can you give me some insight on how the web wrapper app template using both the entryUrl and entryDomain replacement values, where they are used in the app template, and how they are used differently?

I'm pulling the start_url value from manifest.json, and I'm curious how this value best maps onto either entryUrl or entryDomain or both.

domain is just the host, while url is the full url. e.g.:

https://my.example.com/interesting_page.html would be a valid entryUrl while example.com might be a valid entryDomain

[marceloomens]

Sure, but how is that important for and in the template? This is what MDN has to say about the start_url field in manifest.json:

The start_url manifest member is used to specify the URL that should be opened when a user launches your web application, such as when tapping the application's icon on their device's home screen or in an application list.
-- MDN

Based on this, I would suggest setting the entryUrl as the start_url and the entryDomain as the hostname portion of the start_url.

And the same time, in that case it would seem more reasonable not to specify entryUrl as the (mandatory) cli paramater, but instead just ask for a url or website. What do you think?

[daniellacosse]

Sure, but how is that important for and in the template? This is what MDN has to say about the start_url field in manifest.json:

The start_url manifest member is used to specify the URL that should be opened when a user launches your web application, such as when tapping the application's icon on their device's home screen or in an application list.
-- MDN

Based on this, I would suggest setting the entryUrl as the start_url and the entryDomain as the hostname portion of the start_url.

And the same time, in that case it would seem more reasonable not to specify entryUrl as the (mandatory) cli paramater, but instead just ask for a url or website. What do you think?

Yeah, in the case that we have a manfiest.json, that makes sense.

I specified "entry" to clarify what the url was for. An un-prefixed/namespaced "url" might be harder to grok (url for what, exactly?). We can change "entry" to something else if that's better, though. "rootUrl"?

additionally we could support passing a url w/o a flag. e.g. (app-maker https://www.example.com) i think reads well