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
and the new one is using aliasses in pydantic to create custom names as done here: #335
as there is also some case-sensitive property-names the first implementation does not fit all modifications, that should be removed and add pydantic aliasses to all properties that need a rewrite instead.
as for now it seems to be these elements needing to be rewritten to pydantic aliasses:
BGP:
remote_addr: Optional[IPAddress] = None
peer_uptime: Optional[int] = None
Alarm:
alarm_type: Optional[AlarmType] = None
alarm_count: Optional[int] = None
The text was updated successfully, but these errors were encountered:
This issue merits a meeting about all the event/pm attribute names, to generally having better/more descriptive names and then adding the Zino1 names as alias.
There are now two ways that event property-names are modified to match the zino 1 protocol names. the first one is a catch-all rewrite of underscore to dashes: 7caf880#diff-5eef89ad67750f4ac6ef25ea411553bf2bc5dab2d901020b7526ab52b774bf3b
and the new one is using aliasses in pydantic to create custom names as done here: #335
as there is also some case-sensitive property-names the first implementation does not fit all modifications, that should be removed and add pydantic aliasses to all properties that need a rewrite instead.
as for now it seems to be these elements needing to be rewritten to pydantic aliasses:
BGP:
Alarm:
The text was updated successfully, but these errors were encountered: