Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
libpitt opened this issue Jan 31, 2025 · 0 comments

Comments

@libpitt
Copy link
Contributor

libpitt commented Jan 31, 2025

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.

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.

@libpitt libpitt added this to CODCC Jan 31, 2025
@libpitt libpitt converted this from a draft issue Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant