Skip to content

Custom names for more resource types #54

Description

@garethsb

#53 introduced ability for user to specify custom names for Inputs and Outputs and their channels, in the IS-08 Audio Channel Mapping implementation, saved in Local Storage. This feature would also be useful for other resources, such as Nodes, Senders and Receivers.

The complication is that the Channel Mapping filtering is performed entirely client-side, whereas the List views for the IS-04 resource types use server-side queries. A possible approach for searching for labels could be to make a server-side query on both label and id, based on a client-side pass through a mapping in local storage.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions