fix: overriding cache persists cached data in subsequent calls

[NielsJPeschel]

Proposed changes

The behavior of overrideCache should be such that when provided, any subsequent calls should reuse the same promise and or response that follow the new promise that gets created.

However, since we currently do not actually flush the cash, when attempting to override the cache, we have the following behavior:

const res1 = await lazyFetchData()

// some time later

const res2 = lazyFetchData(true);
const res3 = lazyFetchData();
const res4 = lazyFetchData();

res3 and 4 will actually return res1, as res2 has not yet resolved (thereby it has not yet updated useLazyLoadData's internal cache to reflect the new result)

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[nthurow]

So without your changes, r3 and r4 would have both resolved to '1'?

[NielsJPeschel]

Exactly!