You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@leandrost The API is undergoing some breaking changes to conform to the JSON:API spec. They are currently in the staging environment (https://got-board-api-sandbox.herokuapp.com/) for you to test. Let me know once you change the client to the new interface so I can deploy them to production.
Changes:
API
The value of the type identifier is now in singular instead of plural.
Ex: "type" => "order" instead of "type" => "orders"
Game
No longer has the attribute id since there can't be an attribute with the same name as the id identifier [1]. You can still get the identifier via id outside the attributes object.
Creating a game no longer includes all related resources by default. To include them, you will need to list them in the include parameter. Ex: POST /games?include=territories,orders,units,garrison_tokens
The index endpoint has been removed for now.
Territory
No longer has the attribute game_id since they no longer belong to a single game.
No longer has the attribute id since there can't be an attribute with the same name as the id identifier [1]. You can still get the identifier via id outside the attributes object.
The attribute type changed to territory-type, since there can't be an attribute with the same name as the type identifier [1]
House
No longer has the attribute id since there can't be an attribute with the same name as the id identifier [1]. You can still get the identifier via id outside the attributes object.
Order
The attribute type changed to order-type, since there can't be an attribute with the same name as the type identifier [1]
Token
The attribute type changed to token-type, since there can't be an attribute with the same name as the type identifier [1]
Unit
No longer has the attribute id since there can't be an attribute with the same name as the id identifier [1]. You can still get the identifier via id outside the attributes object.
The attribute type changed to unit-type, since there can't be an attribute with the same name as the type identifier [1]
The text was updated successfully, but these errors were encountered:
@leandrost The API is undergoing some breaking changes to conform to the JSON:API spec. They are currently in the staging environment (https://got-board-api-sandbox.herokuapp.com/) for you to test. Let me know once you change the client to the new interface so I can deploy them to production.
Changes:
API
type
identifier is now in singular instead of plural.Ex:
"type" => "order"
instead of"type" => "orders"
Game
id
since there can't be an attribute with the same name as theid
identifier [1]. You can still get the identifier viaid
outside theattributes
object.game
no longer includes all related resources by default. To include them, you will need to list them in theinclude
parameter. Ex:POST /games?include=territories,orders,units,garrison_tokens
index
endpoint has been removed for now.Territory
game_id
since they no longer belong to a single game.id
since there can't be an attribute with the same name as theid
identifier [1]. You can still get the identifier viaid
outside theattributes
object.type
changed toterritory-type
, since there can't be an attribute with the same name as thetype
identifier [1]House
id
since there can't be an attribute with the same name as theid
identifier [1]. You can still get the identifier viaid
outside theattributes
object.Order
type
changed toorder-type
, since there can't be an attribute with the same name as thetype
identifier [1]Token
type
changed totoken-type
, since there can't be an attribute with the same name as thetype
identifier [1]Unit
id
since there can't be an attribute with the same name as theid
identifier [1]. You can still get the identifier viaid
outside theattributes
object.type
changed tounit-type
, since there can't be an attribute with the same name as thetype
identifier [1]The text was updated successfully, but these errors were encountered: