make the data types that are exported in the features object consistent (from the Lua library that outputs the observations to xml to the FeaturesFromSteam class that parses it)
Because
currently we do not have a consistent agreement of the data types of each field (e.g. an aircraft's heading is a string rather than a float)
Complexity
Easy to medium.
Definition of Done
Change the namedtuple objects in features.py to NamedTuple from typing to add typing.
Make data types consistent for fields in features.py and pycmo_lib.lua and fix any tests or demos that might be broke.
Potentially change SteamClientProps from a data class to a NamedTuple class.
We should
make the data types that are exported in the features object consistent (from the Lua library that outputs the observations to xml to the
FeaturesFromSteamclass that parses it)Because
currently we do not have a consistent agreement of the data types of each field (e.g. an aircraft's heading is a string rather than a float)
Complexity
Easy to medium.
Definition of Done
namedtupleobjects infeatures.pytoNamedTuplefromtypingto add typing.features.pyandpycmo_lib.luaand fix any tests or demos that might be broke.SteamClientPropsfrom a data class to aNamedTupleclass.