Proposed changes

If the fetchData function passed to useLoadData throws a synchronous exception, then useLoadData should handle that and should return an initial state of "error". Previously, useLoadData was not handling this scenario and a fetchData function that threw a synchronous exception would result in an unhandled exception.

For example, the following scenario currently throws an unhandled exception:

useLoadData(() => {
  throw 'an error';
});

This PR allows the above scenario to be correctly handled such that useLoadData would simply return:

{
  inProgress: false,
  result: undefined,
  isError: true,
  error: 'an error'
}

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