Add onError callback to useAsset

[trezy]

Description of change

This adds an onError callback to the useAsset hook. This allows us to handle errors within the related component instead of requiring an error boundary.

Fixes: #501

Pre-Merge Checklist

• Documentation is changed or added
• Lint process passed (npm run lint)

[trezy]

@thejustinwalsh, I'd love feedback from you on the solution here.

[thejustinwalsh]

My initial thoughts are that if you throw to the suspense boundary and use the callback for error handling, you won't be able to stop the hook from executing again. Would you?

I was curious if we need a pattern that is more like reactQuery where you have two hooks...
useAsset(s) and useSuspenseAsset(s)

const { isPending, isError, data, error } = useAsset("my-awesome-sprite.png");
// or
const sprite = useSuspenseAsset("my-awesome-sprite.png");

Would make it very clear that you are opting into suspense, and if not, you have a nice pattern for handling the loading state within the component the OG way.

FWIW, I am super into suspense and like typing fewer characters for my hook, but I don't think Suspense is the typical pattern in the react-pixi community today. Folks upgrading would have a better time with a non-suspense hook out of the gate until they jump on the suspense train.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 8c78809:

Sandbox	Source
pixi.js-sandbox	Configuration

[github-actions]

🎉 This issue has been resolved in version 8.0.0-beta.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀