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

Setting maskedErrors to true in development mode has no effect #3330

Open
kireerik opened this issue Jun 21, 2024 · 2 comments
Open

Setting maskedErrors to true in development mode has no effect #3330

kireerik opened this issue Jun 21, 2024 · 2 comments

Comments

@kireerik
Copy link

kireerik commented Jun 21, 2024

Describe the bug

See the title.

Your Example Website or App

Steps to Reproduce the Bug or Issue

Do what the title says.

Expected behavior

The setting is respected.

Screenshots or Videos

No response

Platform

  • OS: Windows
  • NodeJS: 20.14.0
  • graphql-yoga version: 5.3.0

Additional context

No response

@n1ru4l
Copy link
Collaborator

n1ru4l commented Jun 21, 2024

Can you please explain in detail what you expect to happen? An example GraphQL response of what you get today, and what you expect instead with the setting set to true?

@kireerik
Copy link
Author

Sure. Let's say i throw an error like this (in a GraphQl query):

throw Error('test')

This is what I get as a response:
Unexpected error. on errors[0].message (This is as expected.)

errors[0].extensions(.originalError (with the relevant details on it in message and stack))

I expect to get no extensions at all (in this case) but more impotantly no originalError on it (in this case).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants