Skip to content

[Task]: Unify transports constants usage #705

@ishymko

Description

@ishymko

Currently transport names are defined in two different ways in constants.py and both have some usage across the codebase.

Seems like the class was a leftover from Pydantic data model where it was defined like | in the JSON Schema. given that custom protocols can be defined we can just use strings constants to make it look the same way for both system-provided and user-defined.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions