fix: empty dataResults causes "no corresponding fetcher result"

[ZxBing0066]

When requests are aborted, it should always return a valid dataResults; otherwise, processLoaderData throws the "Did not find corresponding fetcher result" error.

Introduced by this PR.

fixes #13712

[changeset-bot]

⚠️ No Changeset found

Latest commit: a9848d7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[remix-cla-bot]

Hi @ZxBing0066,

Welcome, and thank you for contributing to React Router!

Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once.

You may review the CLA and sign it by adding your name to contributors.yml.

Once the CLA is signed, the CLA Signed label will be added to the pull request.

If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected].

Thanks!

- The Remix team

[remix-cla-bot]

Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳

[timdorr]

Can we add a test for this? Preventing regression is really important in cases like this.

[ZxBing0066]

@timdorr Test added. Please help review.

[ZxBing0066]

The failed test seems to be a flaky one. I also see it in other PR.