change default cache resolver

the default cache resolver simply does a JSON.stringify test against the old and new parameters. This does not take into account the position of the properties and can lead to false results (depending on your point of view).

If you were to use object-hash to compare the two objects this is no longer an issue. See the code sample below

const hash = require('object-hash');

const p1 = { d1: 'd1', d2: 'd2' };
const p2 = { d2: 'd2', d1: 'd1' };

const hash1 = hash(p1);
const hash2 = hash(p2);

console.log('json', JSON.stringify(p1) === JSON.stringify(p2));
console.log('hash', hash1, hash2, hash1 === hash2);

the result of this is

json false hash f4c434a0e4c11deb776f4281c9b3848ccbe63578 f4c434a0e4c11deb776f4281c9b3848ccbe63578 true

this could be implemented by default , or by adding an option to specify a different cache resolver so that it won’t break existing code that relies on key position creating different cache results

[angelnikolov]

Let me think about that… That’s quite a jump for a 6kb library. It drags along crypto which is pretty big. I feel like the benefit we gain from adding this compare to what we lose is smaller and is something that can be mitigated by a better documentation, i.e - if you want your cache to resolved properly for object parameters, they should have the same shape.

[Ayushidawada]

@angelnikolov Can you please give me an example of using cacheResolver and cacheHasher and its difference,As i am using your package for my project,as of now not facing any issue while using other configurations except this two.