Describe the bug
When testing our staging room we found out that even though we are getting a positive response from the server(No HTTP error what so ever, instead we got the expected Game Object) . The password would not get updated and it remained possible to join the game with the old password (New one does not work).
To make sure our code was not causing the issue we recreated the process only using Swagger and still were not able to change the password
To Reproduce
Steps to reproduce the behavior:
Open 2 Swagger Tabs (put both of them next to each other, its way easier that way)
Log into both on different account. We used my personal account on one and "string" on the other
Verify they are correctly authorized (Get games for example)
Create game with one account. Make sure started is set to false and put the password "123"
Patch the game, by removing everything except for the password field (All fields are optional) and put the password as "1234"
Verify getting a positive code 200 response
Joining the game with the other account using password "123" ( Leave "traits" as an empty list and "color" as "#000"
Verify using the get game members endpoint that you have in fact joined the game
Expected behavior
It is expected that you could not join the game and would receive a code 403 "Incorrect password." error.
Additional context
The new password also does not get recognized. Its use resulting in a 403 error instead.
Describe the bug When testing our staging room we found out that even though we are getting a positive response from the server(No HTTP error what so ever, instead we got the expected Game Object) . The password would not get updated and it remained possible to join the game with the old password (New one does not work). To make sure our code was not causing the issue we recreated the process only using Swagger and still were not able to change the password
To Reproduce Steps to reproduce the behavior:
Expected behavior It is expected that you could not join the game and would receive a code 403 "Incorrect password." error.
Additional context The new password also does not get recognized. Its use resulting in a 403 error instead.