Skip to content

Support for nested field types in computed fields #149

@mshick

Description

@mshick

Right now if I have a computed field and I'd like to return a non-primitive value I have to use json as the type. Ideally I'd be able to use a nested field definition to provide stronger typing for computed fields.

Related to #91 in that this would bring computed fields in line with regular fields.

Metadata

Metadata

Assignees

No one assigned

    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