Skip to content

object field input mappings expected to be complete but enums and output are not #5

Description

@metagn

Copied over from holo-nim/holo-json#13

Ideally users can use the output of defaultFieldMappings and modify it rather than typing each individual field. But object field output and both enum field input and output support incomplete mappings already, it's just object input field mappings that don't. And iterating over fields twice might have a performance penalty.

On the other side the final iterators can just use getTypeImpl instead of getTypeInst.

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