You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently don't do anything when the incoming Query has a property on a QNode or QEdge that isn't explicitly-listed in the TRAPI 1.3 spec (see links for QNode and QEdge).
However, the implementation rules that TRAPI APIs are supposed to follow says that we should:
generate a TRAPI log (WARNING level). Something like "We've encountered one or more properties on a QNode that we don't recognize: {list them}. We will ignore them and continue execution." for QNode (and similar for QEdge)
proceed (aka ignore them)
Note that some Translator devs use QNode.name to give a human-readable label to their QNode. I think it's okay to give a warning on this - since we don't do anything with this "name" right now.
The text was updated successfully, but these errors were encountered:
We currently don't do anything when the incoming Query has a property on a QNode or QEdge that isn't explicitly-listed in the TRAPI 1.3 spec (see links for QNode and QEdge).
However, the implementation rules that TRAPI APIs are supposed to follow says that we should:
Note that some Translator devs use QNode.name to give a human-readable label to their QNode. I think it's okay to give a warning on this - since we don't do anything with this "name" right now.
The text was updated successfully, but these errors were encountered: