Simplify/optimize map-reduce in useLoadData

[baker-ling]

Proposed changes

I saw the usage of map-reduce in useLoadData, and I think that those can be simplified by using Array.prototype.every and Array.prototype.some instead.

In addition to the simplification, this should provide some time and space optimization.

• Time: .some() and .every() will terminate early (still O(n) though)
• Space: should also be reduced from O(n) to O(1) because they do not build a new array like .map() does

Fixes #41

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...

[CLAassistant]

All committers have signed the CLA.

[nthurow]

It looks good to me! Do the tests work locally? Looks like we don't have those running as a PR check yet...

[baker-ling]

All the tests in useLoadDatat.test.ts pass. Here's the report from running yarn jest useLoadData:

I haven't tried testing it in an application or in a performance test bed.

[NielsJPeschel]

@baker-ling great contribution! Looks like there is a pending contributor license agreement that needs to be signed. Feel free to reach out if you have any questions!

[baker-ling]

@baker-ling great contribution! Looks like there is a pending contributor license agreement that needs to be signed. Feel free to reach out if you have any questions!

@NielsJPeschel I think there's an issue with my GH account. I used my Optum email in git when I created the commit, but GH won't let me add my Optum email to my GH account.

I've completed the license agreement several times, so I think this email issue is preventing the PR condition from passing.

[baker-ling]

@NielsJPeschel @nthurow I got the email and CLA issues sorted, so I think it's ready to go.