-
-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(react-router): loader promise not resolving when error thrown in params.parse
#2682
Open
vishwamartur
wants to merge
1
commit into
TanStack:main
Choose a base branch
from
vishwamartur:fix-loader-promise
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Related to TanStack#2514 Add test to verify `notFoundComponent` is displayed when an error is thrown in `params.parse` in a child route. * Add a new test case in `errorComponent.test.tsx` to check if the `notFoundComponent` is rendered when an error is thrown in `params.parse`. * Create a root route with a `notFoundComponent`. * Create an index route with a link to a child route. * Create a child route with a `params.parse` function that throws an error for a specific condition and an `onError` function that re-throws the error as `notFound()`. * Render the router and simulate a click on the link to the child route. * Verify that the `notFoundComponent` is displayed.
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 4050e58. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution
✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
is this testing the same thing as #2636 ? |
SeanCassiere
changed the title
Fix loader promise not resolving when error thrown in params.parse
fix(react-router): loader promise not resolving when error thrown in Oct 31, 2024
params.parse
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #2514
Add test to verify
notFoundComponent
is displayed when an error is thrown inparams.parse
in a child route.errorComponent.test.tsx
to check if thenotFoundComponent
is rendered when an error is thrown inparams.parse
.notFoundComponent
.params.parse
function that throws an error for a specific condition and anonError
function that re-throws the error asnotFound()
.notFoundComponent
is displayed.