This repository was archived by the owner on Apr 6, 2023. It is now read-only.
fix(nuxt): preserve error.data in response#4755
Merged
Conversation
✅ Deploy Preview for nuxt3-docs canceled.
|
error.data in response
Merged
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.
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
createError does not return data nuxt/nuxt#13881
❓ Type of change
📚 Description
The current error
errorhandlerimplementation does not put the data object into the response. By adding thedataobject received from the_errorobject to theerrprObjectwe can add the data to the response. This fixes nuxt/nuxt#13881.It is not required to check if the object exists, as it will automatically not be appended to the
errorObjectif it is undefined.📝 Checklist