Even tho the Lobby class has a data field where you can put any data you want in the form of a Dictionary<string, string>, it wasn't possible to pass this field along the creation of the Lobby, or even updating it. This fixes that by changing the lobby API to use our auto-gen API for Lobby, instead of directly calling the requests.
Checklist
[x] Have you added appropriate text to the CHANGELOG.md files?
Add those to list or remove the list below altogether:
When you are merging a feature branch into main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging from main to staging, or staging to production, please use a regular merge commit.
Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?
Ticket
resolves #3312
Brief Description
Even tho the
Lobbyclass has adatafield where you can put any data you want in the form of aDictionary<string, string>, it wasn't possible to pass this field along the creation of theLobby, or even updating it. This fixes that by changing the lobby API to use our auto-gen API for Lobby, instead of directly calling the requests.Checklist
Add those to list or remove the list below altogether:
Notes
When you are merging a feature branch into
main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging frommaintostaging, orstagingtoproduction, please use a regular merge commit.Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?