Skip to content

Conversation

@tarrow
Copy link
Contributor

@tarrow tarrow commented Jan 31, 2025

We saw one case of errors appearing in JSON responses breaking their parsing[1]. This commit should disable displaying (in the response) but not disable all
reporting[2].

[1] magnusmanske/quickstatements#58
[2] https://stackoverflow.com/a/21699794

We saw one case of errors appearing in JSON responses
breaking their parsing[1]. This commit should disable
displaying (in the response) but not disable all
reporting[2].

[1] magnusmanske/quickstatements#58
[2] https://stackoverflow.com/a/21699794
@deer-wmde
Copy link
Contributor

Hm I think we might want this only in production, so we still spot errors in local/staging envs?

@tarrow
Copy link
Contributor Author

tarrow commented Jan 31, 2025

I think we would probably be ok with this in any environment; as I understand it we will still get errors in all the different environments logs. Locally we probably also don't want deprecation warning polluting supposedly valid json responses

@deer-wmde deer-wmde merged commit fa92163 into main Jan 31, 2025
3 checks passed
@deer-wmde
Copy link
Contributor

true, also this maybe could be a security risk

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

Successfully merging this pull request may close these issues.

3 participants