Re: [w3c/manifest] Should the scope terminate by "/"? (#554)

I don't think it's reasonable to ask web site developers to rename their entire site around the fact that there's a deficiency in what should be a very simple path scope match.

True, `/maps` and `/maps/` are not the same. I'm not asking for them to be the same. I'm asking for a mechanism that does not force the developer to consider `/mapsearch` a child of `/maps`. No reasonable software developer would ever expect `/mapsearch` to be a child node of `/maps` in a path hierarchy.

A good example is if you had a PWA at `/warcraft` and then you wanted to make `/warcraft2`. You'd realise you're stuck because `/warcraft2` is inside the `/warcraft` PWA scope, and there's no sensible other name for that directory.

Anyway, I've spoken with @slightlyoff and @jakearchibald and it looks like (for this and other reasons) we want to introduce "auxiliary scopes" (so you can specify multiple separate scope paths which can be either prefix match or exact match). That would solve this issue. This was for SW, but we can introduce the same concept into Manifest, to match.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/554#issuecomment-371692572