Skip to content
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

createError Utility Response Does Not Match Documentation #27697

Closed
Ray0907 opened this issue Jun 19, 2024 · 2 comments
Closed

createError Utility Response Does Not Match Documentation #27697

Ray0907 opened this issue Jun 19, 2024 · 2 comments

Comments

@Ray0907
Copy link

Ray0907 commented Jun 19, 2024

Environment

  • Operating System: Darwin
  • Node Version: v20.12.2
  • Nuxt Version: 3.12.2
  • CLI Version: 3.12.0
  • Nitro Version: 2.9.6
  • Package Manager: pnpm@8.15.7
  • Builder: -
  • User Config: ssr, runtimeConfig, app, vite, nitro, modules, auth, i18n, dayjs
  • Runtime Modules: @sidebase/nuxt-auth@0.6.7, @nuxtjs/i18n@8.3.1, dayjs-nuxt@2.1.9, @nuxt/test-utils/module@3.13.1
  • Build Modules:

Reproduction

as desc

Describe the bug

I’m following the documentation at https://nuxt.com/docs/api/utils/create-error, but the API response does not match, even when I use statusCode and statusMessage or follow the h3 documentation for status and message.

I encountered two problems:

1.	The status code always returns 400, regardless of the value I set for statusCode or status.
2.	The message (statusMessage) includes the stack trace.

Additional context

No response

Logs

No response

Copy link
Contributor

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

Copy link
Contributor

This issue was closed because it was open for 7 days without a reproduction.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants