gameontext / gameon-player Goto Github PK

The player filter was written to protect the original player api using jwts.

We've since added a bunch of additional api's to player, and didn't update the filter.

In the most case, this worked fine, because the filter essentially said 'if it's only a get request, and has no query params, allow it anyway' ..

Sadly, some of the new api's need query params, so filter needs an upgrade.

Today we only accept jwt's passed in the custom gameon-jwt header, we should also accept Authorization Bearer usage of jwts to enable easier integration with caller frameworks.

If a player record is deleted, the api-key for the player will be deleted too.
Unfortunately this means any remaining rooms created by the player can no longer be removed by the player because they have no api-key.

Deleting a player should also locate and remove all rooms owned by the player too.

Hi Erin,

Just to remember to fix the swagger for the GET request to list all players to include the type that will be returned , so I can see the information (id) in response.

Should be this guy coming back in the list:
PlayerArgument {
_id (string): Unique player id ,
name (string): Player name ,
favoriteColor (string): Favorite color
}

Thanks,

Should be using an encoder/decoder to consistently parse out the routing information: we can then use the result object for testing, rather than passing around an obscure array.

Save player names & emails so we can contact them with updates.