Why does everything in the API return a game?

[kenan-rhoton]

Currently we have 4 API calls:

• POST to /games: Returns an entire game-as-player object, when only the game-id and player-id are needed.
• POST to /games/:game-id/: Returns an entire game-as-player object when only player-id or error are needed.
• POST to /games/:game-id/player/:player-id: Returns (guess what?) and entire game-as-player object when only ok or error are needed. Also, this should be a PUT call (my bad).
• GET to /games/:game-id/player/:player-id: Returns an entire game-as-player which is exactly what we want.

So 3 of the 4 calls return unnecessary stuff and on top of that actually require specific logic to implement returning this unnecessary stuff (save-game has an extra line *just to return the saved-game object`)

We should limit the calls to only return what they need. This will possibly require some frontend adaptation.

[Masclins]

I don't understand what POST, GET nor PUT means.

[kenan-rhoton]

http://www.restapitutorial.com (it's in CONTRIBUTING.md)

[ruchnar]

I guess "we" will need to change frontend acording to those REST calls.
EDIT: nevermind, just saw your last line, Kenan

[pernilsalat]

i'd like to have a try with this one

[kenan-rhoton]

done!

[Masclins]

@pernilsalat how's this going on?

[kenan-rhoton]

I'll release v0.1.1 without this if it's not done today, we need to focus on v0.2.0

[Masclins]

Maybe this has sense to be worked together with #78 (which is supposed to also be done by @pernilsalat, so everything's good)