@patrickkwang mentioned that this should be type. OpenAPI docs do not have either of these documented for the specification for edges. Currently, the UI has been implemented assuming that the predicate term will be returned under type.
On a related note, @cbizon , @kennethmorton - Is there any conceivable reason why one might have more than one predicate on an edge? This would impact whether the type of the type param can simply be a string or whether it should be a list of strings. Currently it's been implemented to support a list of strings.
@patrickkwang mentioned that this should be
type
. OpenAPI docs do not have either of these documented for the specification for edges. Currently, the UI has been implemented assuming that the predicate term will be returned undertype
.On a related note, @cbizon , @kennethmorton - Is there any conceivable reason why one might have more than one predicate on an edge? This would impact whether the type of the
type
param can simply be a string or whether it should be a list of strings. Currently it's been implemented to support a list of strings.