inMemoryCache key too vague
The inMemoryCache keys currently just used the path of the requested resource. The issue with that is that the resultant data returned is based on more than just the path. The cache key should be updated to include the following options:
- leaveMangledNames
Proposed change to the key:
let cacheKey = `${path}?leaveMangledNames=${!!leaveMangledNames}`
Edited by Caleb Weeks