fix: throw error if non-POJO is an error #18
Conversation
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
|
Hey, is there any chance we can merge this pull request? 😄 |
|
+1, we just ran into this issue in Astro as well moving from |
|
+1 |
|
cc @pi0 |
|
Can this be merged? It's been almost a year now. |
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.
This pull request gives a better UX to a developer using nuxt. Right now, if an error is thrown and that cannot be stringified, the only thing shown is the error name —for example:
TypeError—. With these changes, if the thing that is being stringified is an error, instead of just showing the name, the error is re-thrown, with an extended error message.