Skip to content

TRACKER: For filter properties feature, consider on_read_trigger and dependency_properties #591

@libpitt

Description

@libpitt

Original feature cards:
sennetconsortium/portal-ui#1806
#580

If there is a case where a property could have on_read_trigger in yaml, but is also stored in neo4j, (then need specific flag/option in yaml to indicate trigger field. "on_read_trigger" in entity_properties[p]

If add a field who dependency is not in the list of defaults, then need to either add to defaults or add option dependency_properties to the respective field in the yaml.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions