fix: createError fallback to statusMessage #25
Merged
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.
Currently, when using Nuxt, the createError does not generate meaningful error messages if only
statusMessage
is provided (which I see is more commonly been used in the Nuxt code base)I would think it could be better to serve
statusMessage
ifmessage
is not provided. Ideally, maybe we could have better format as`${input.statusCode}: ${input.statusMessage}`
but I will leave it for discussions