Skip to content

generalized field keys instead of just string names? #7

Description

@metagn

i.e. allow mapping fields to 1, 2, 3 or Enum1 Enum2 Enum3. The way field mappings work is not generic though.

Strings already work as a universal key representation especially at compile time, but it might lower performance to convert data to strings at runtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    usabilityproblem with the practicality of the current design/implementation

    Type

    No type

    Fields

    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