Skip to content

metadata usage in api.py does not follow jack api directly #5

@falkTX

Description

@falkTX

This goes against the initial ideas for this library, where the jack api is mapped 1:1 as much as possible.
We need to have those handy utils on top of the metadata stuff to make them usable, but that should be on a separate file in order to keep consistency in the project.

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