Skip to content

OMBC.Status, different Value Type for active_operation_mode_id and prior_operation_mode_id #118

@realdognose

Description

@realdognose

In the OMBC.Status, the properties active_operation_mode_id and prior_operation_mode_id
are implemented as type ID, not UUID like all the other ids.

Setting a UUID there causes validation-errors, which is quite unhandy, because OMBCOperationMode is using UUID as id.

Image

Image

<class 's2python.ombc.ombc_status.OMBCStatus'>, (), 'active_operation_mode_id\n  Input should be a valid string (type=string_type)', 1 validation error for OMBCStatus
active_operation_mode_id
  Input should be a valid string [type=string_type, input_value=UUID('1599e4c2-a48d-43e2-9ffd-d272ea54e34e'), input_type=UUID]
    For further information visit https://errors.pydantic.dev/2.11/v/string_type)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions