You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The web-app-origin-association file's "paths" field currently only supports wildcard characters at the end of the path. For example:
"paths":["/"]
"paths":["/documents/"]
However, if I specify a path such as ["*/news"], this is unsupported as the wildcard character is not at the end of the path.
Can you please consider supporting wildcard characters at the beginning of paths too? This will be useful for applications whose paths may be dynamic with data such as an identifier/username/location but have a common suffix path. For example, "/usa/news" and "/uk/news", which can be specified as ["*/news"].
The text was updated successfully, but these errors were encountered:
I think this is a good idea that will not negatively impact performance (both prefixes and suffixes are easy to match). Developers should have more flexibility in syntax to define the set of paths to include or exclude.
I'll open a PR shortly to address this.
The web-app-origin-association file's "paths" field currently only supports wildcard characters at the end of the path. For example:
"paths":["/"]
"paths":["/documents/"]
However, if I specify a path such as ["*/news"], this is unsupported as the wildcard character is not at the end of the path.
Can you please consider supporting wildcard characters at the beginning of paths too? This will be useful for applications whose paths may be dynamic with data such as an identifier/username/location but have a common suffix path. For example, "/usa/news" and "/uk/news", which can be specified as ["*/news"].
The text was updated successfully, but these errors were encountered: