opened
jeffposnick
username_0
R: @addyosmani @gauntface 
CC: @HenrikJoreteg @liuruoran88

This fixes #714 by explicitly changing the method call inside of `WorkboxSW` to indicate that for the internal `CacheOnly` handler use for precached requests, `cacheId` shouldn't be prepended when determining the corresponding cache name.

I decided to go with that approach rather than making a chance in the `RequestWrapper` constructor that checked to see if `cacheId` was already present in the `cacheName`, since you could theoretically imagine calling

```js
new RequestWrapper({
  cacheName: 'my-prefix',
  cacheId: 'my-prefix',
}});
```

In that situation, the user would expect the effective cache name to be `'my-prefix-my-prefix'`, and we'd want to still allow that.
Fix for multiple cacheId prefixes in the precache handler
issue
created
jeffposnick
username_0
The interplay of `cacheId` and `cacheName`, while useful, definitely complicates the logic, too.
comment