Skip to content

Explicit API #5

Description

@neu-rah

Libraries based on OneLib::OnePin should receive the API object explicitly instead of the current implicit access.

because implicit causes ambiguities when mixing frameworks/api's

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions