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
Following from PeterJCLaw/srcomp#27 it seems that this repo relies on the ordering of the keys in the mapping returned from /corners is the same as the order of the list of teams in a match. This appears to currently work, however this is due to us always naming corners 0, 1, 2 and 3in that order.
It is unclear whether this is something that should be relied upon -- specifically whether JSON & JavaScript mappings' keys have defined stable orderings.
The text was updated successfully, but these errors were encountered:
Following from PeterJCLaw/srcomp#27 it seems that this repo relies on the ordering of the keys in the mapping returned from
/corners
is the same as the order of the list of teams in a match. This appears to currently work, however this is due to us always naming corners0
,1
,2
and3
in that order.It is unclear whether this is something that should be relied upon -- specifically whether JSON & JavaScript mappings' keys have defined stable orderings.
The text was updated successfully, but these errors were encountered: