Skip to content

Fix the mashup between mandatory and optional arguments in device class constructors #2

Description

@zserg8

Currently there is a bit of a mix of what is declared optional and what mandatory on the controller class level and on the device class level. This has to be aligned and likely loosened a bit (e.g. making device name non-mandatory)

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions