Closed viniarck closed 1 year ago
After more consideration, it's not worth it during this iteration, so I'll close it for now. It'll be kept as it is, and then we'll make sure that if any API changes, then it'll need to be updated on affected clients too.
If we were to map
EVC
as a model internally, it'd be less error prone when using theevc: dict
structure, currently we're making a lot of dict key access.mef_eline
won't break its API, so that isn't a concern, but it'd be handy to also have the model for linting type completions. Also,telemetry_int
is mapping the EVC uni with slightly different properties to also derive the switch and port number given an interface_id, so having a model we also parse and structure it accordingly