anchor.diff:  
           {
               "match": {
  +                "_id": "5474476a96af22405e619ec0",
                   "game_id": "541715e10476afa004fc3b82",
                   "status": "running",
                   "description": "Sample match for testing",
  -                "custom_properties": {
  +                "customProperties": {
                       "type": "coop"
                   },
  -                "max_players": 2,
  +                "maxPlayers": 2,
                   "players": [
                       "5474476a96af22405e619ebe"
                   ],
  -                "global_state": {},
  -                "last_event_id": 0,
  -                "events": [],
  -                "match_id": "5474476a96af22405e619ec0"
  +                "globalState": {},
  +                "lastEventId": 0,
  +                "events": []
               }
           }
   
  
positive.code:                 "move": {
                      "what": "changed"
                  },
                  "global_state": {
                      "full": "game_state"
                  }
              }
  
negative.code: 
  ### Filtering by properties
  
  Matches contain an user defined field named `customProperties`, which can be used by developers to store and fetch additional details about a game. In the example of a card-based game, one of these properties could store the minimum bet. This information could also be used to help players to join games best suited to their willing. A filter is specified as an URL-encoded JSON containing attributes and the corresponding expected value. No comparison operators are available for now, now is it possible to customize the implementation : when there are more than one attributes, all conditions specified must be met in order for the match to qualify.
  
  The following will return the matches which have a property named type with value being "coop".
  `GET /v1/gamer/matches?properties={"type": "coop"}`
  