Closed jpelay closed 2 weeks ago
We've found another error, I will solve this tomorrow!
@Annelein I fixed the achievements issue! Can you check again please?
@jpelay I've changed some 204's to 200's, because the make_response
might not have content, but there might be a check for response.achievements
on the frontend, which will result in an error if it's a 204.
Only comment left is about response
instead of response_body
, otherwise I will approve!
**btw I can also add a check in the frontend for response and then make it a 204 instead?
@jpelay I've changed some 204's to 200's, because the
make_response
might not have content, but there might be a check forresponse.achievements
on the frontend, which will result in an error if it's a 204.
Perfect, thanks!
Only comment left is about
response
instead ofresponse_body
, otherwise I will approve!
What's the comment?
Thank you for contributing! Your pull request is now going on the merge train (choo choo! Do not click update from main anymore, and be sure to allow changes to be pushed to your fork).
Thank you for contributing! Your pull request is now going on the merge train (choo choo! Do not click update from main anymore, and be sure to allow changes to be pushed to your fork).
5558 Introduced an error where some calls where expecting a JSON, and got text instead. I checked the places where this happened and fix the calls.
If I'm missing some, please add them 😄
How to test Perform the following:
And all of them should show the success modal!
Also: Fixes #5550