In the context of a draft, it's useful to know how many slots are available for each position. Within the API, this information is available as part of the mSettings view:
// psuedo-JSON response
{
....
rosterSettings: {
...
lineupSlotCounts: {
"0": 1, // maps to "QB" slot
"1": 0, // maps to "TQB" slot
"2": 2, // maps to "RB" slot
... etc, goes all the way to slot 24
}
}
}
We can map each lineupSlotCount(s) to it's respective position and provide this information to the consumer:
In the context of a draft, it's useful to know how many slots are available for each position. Within the API, this information is available as part of the
mSettings
view:We can map each lineupSlotCount(s) to it's respective position and provide this information to the consumer: