Skip to content
Discussion options

You must be logged in to vote

Agreed that simply returning 500 is not the ideal behavior. Thanks for this suggestion!
I think the status code 400 would be the most suitable here. I've created an issue for our product team to pick up so you can expect the behavior to change in a next version.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by hugoqribeiro
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
BFF
Labels
None yet
3 participants