Support WebManifest shortcuts when generating the TWA

[rayankans]

No description provided.

[PEConn]

What's the UX here? We're prompting to ask if the developer wants to include shortcuts and then what?

What if the developer selects yes and there are no shortcuts in the web manifest? Do we let them specify some?

[rayankans]

What's the UX here? We're prompting to ask if the developer wants to include shortcuts and then what?

I had an offline conversation with @andreban about this. Currently, we just ask whether users want to include shortcuts or not. They can't set it themselves. If we do end up going down that path, we will need to explore some UI possibilities, as it's not that easy to set them up via a CLI. It's easier to pass a file manifest if you want to customize shortcuts in a way that differs from the published Web Manifest.

If they select yes and there are no shortcuts, nothing happens.

[andreban]

Yes, filling a shortcuts section from the prompt might make things complicated (maybe we could make it optional later).

It's possible to add an ask attribute to the configuration and add a function that will only trigger the question if a shortcuts section exists in the Manifest. https://github.com/flatiron/prompt/blob/master/examples/dynamic-ask-prompt.js#L14-L17

I wonder if we should show developers the content of the existing shortcuts before asking them to confirm.

[rayankans]

Makes sense, I added the ask condition, and the shortcut is now displayed. So if there are no shortcuts, no prompt shows up. Here's what it looks like if there are in fact shortcuts in the manifest