Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scope extensions explainer: Avoid adding web to names #28

Open
kenchris opened this issue Aug 16, 2021 · 1 comment
Open

Scope extensions explainer: Avoid adding web to names #28

kenchris opened this issue Aug 16, 2021 · 1 comment
Labels
scope-extensions https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md

Comments

@kenchris
Copy link

Though the spec is called Web App Manifest, the web generally doesn't add "web" in API names, like currently used in the explainer, both as "web_apps" key and in the file name "web-app-origin-association.json".

We have even tried to avoid "app" when doable, but it seems that now the "id" proposal might even end up adding "app_id" key as Marcos' suggestion.

Maybe we could just call the file for "origin-association.json"? or "originlinks.json" which is similar to assetlinks.json. Anyway, the shorter the name, the more change that people will get the name right, I assume.

"web_apps" also doesn't say much, maybe something like "extensions" instead, or "allowed_extensions"

@alancutter alancutter added the scope-extensions https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md label Aug 20, 2021
@kenchris
Copy link
Author

kenchris commented Oct 1, 2021

or maybe "scope_inclusions" instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope-extensions https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md
Projects
None yet
Development

No branches or pull requests

2 participants