ericblade / mws-advanced / 111

88%

master: 88%

push

travis-ci

fix for potential cache stampede

- cache API call promises, and return those promises, so that even if
  multiple identical requests are in flight simultaneously for a response,
  only the first one will actually go to the API, and all the rest will
  be resolved automatically when the first request is resolved.
- if the cached data needs further processing (ie digResponseResult) before
  it can be returned to the internal mws-advanced API, then overwrite the
  promise in the cache with the actual data returned, once it is available.
- once the original promise is resolved, it will also return the
  digResponseResult or the returnRaw result, whichever is asked.
- hmm. we may need to add { ...opt } to the cache key string.. need to test

184 of 230 branches covered (80.0%)

Branch coverage included in aggregate %.

443 of 523 relevant lines covered (84.7%)

46.85 hits per line