M
Mark Tarry
Where two blueprints have a relationship, we must explicitly set the identifiers of each entity to be linked.
I'm proposing something more dynamic - enabling an entity (blueprint A) to be related to one or more entities (blueprint B) based on Search & Query syntax.
For example: we want to have a list of "Contributors" to the repository.
Given:
* a
github_repository
blueprint
* a
pull_request
blueprint
* and a
github_credentials
blueprint
It would be valuable to be able to define a property (aggregate/calculation/other) on
github_repository
which could list out all
github_credentials
, related to the repo via the
pull_request
path, with optional filtering (i.e. only PRs in the last 6 months).