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
Right now the set.Decks structure is composed of a few main elements (among which sealedProductUuids, name, and code) and three (or four if we count bonus) array of cards all on the same level
I think the structure could be optimized a bit to separate the main deck properties from the list of cards themselves, as in
In this way third party users can unmarshal cards in a dictionary and map, and just update the list of key present instead of hardcoding a new field. This also has the advantage of removing unused fields in case sideboard or other elements are empty
what do you think?
The text was updated successfully, but these errors were encountered:
Right now the set.Decks structure is composed of a few main elements (among which
sealedProductUuids
,name
, andcode
) and three (or four if we count bonus) array of cards all on the same levelI think the structure could be optimized a bit to separate the main deck properties from the list of cards themselves, as in
In this way third party users can unmarshal
cards
in a dictionary and map, and just update the list of key present instead of hardcoding a new field. This also has the advantage of removing unused fields in case sideboard or other elements are emptywhat do you think?
The text was updated successfully, but these errors were encountered: