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
I submitted the following query to ARAX through the ARS and received an error that the query graph was not interpretable. Please let me know if there was any issue with my query_graph.
Clearly we need to improve our validation and error reporting. The problem with your query_graph is here:
"curie:":"DOID:0050427"
The key has a colon in it ( "curie:" instead of "curie")
If you remove that, it works.
I will add validation of the input message. I thought our framework did this. Ah, but with additionalProperties: true, having things like "curie:" is legal. And having no "curie" is legal. I will add code that will complain about unexpected keys.
@MarkDWilliams I have just pushed a fix so that the following warnings are displayed with the above input query_graph:
2020-12-02 22:49:22.762145 WARNING: Query graph node 'n0' has an unexpected property 'curie:'. Don't know what to do with that, but will continue
2020-12-02 22:49:22.762152 WARNING: Query graph node 'n1' has an unexpected property 'set'. Don't know what to do with that, but will continue
I submitted the following query to ARAX through the ARS and received an error that the query graph was not interpretable. Please let me know if there was any issue with my query_graph.
https://ars.transltr.io/ars/api/messages/30fed63c-aa5b-4ba8-8874-5a458b5d0404
The text was updated successfully, but these errors were encountered: