This repository was archived by the owner on Apr 6, 2023. It is now read-only.
fix(nuxt): use more specific FetchError for useFetch errors#7435
Merged
Conversation
danielroe
added
bug
✅ Deploy Preview for nuxt3-docs canceled.
|
pi0
approved these changes
Sep 12, 2022
Member
pi0
left a comment
pi0
left a comment
There was a problem hiding this comment.
Looks good to me. However, currently, if interceptors fail for example we don't throw a network error. But is fixable for most cases.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
🔗 Linked issue
resolves nuxt/nuxt#14879
❓ Type of change
📚 Description
In the case of
useFetch, errors will almost certainly be of theFetchErrortype so we can provide a bit more type hinting to the user to avoid the requirement of casting...📝 Checklist