We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I get 500 errors when trying to use jmespath for the following queries.
GET version
POST version:
curl --location --globoff 'https://mychem.info/v1/query?size=1000&fields=chembl.molecule_chembl_id,chembl.drug_mechanisms&jmespath=chembl.drug_mechanisms.target_components|[?uniprot=='Q16602']' \ --header 'Content-Type: application/json' \ --data '{ "q": ["Q16602"], "scopes": ["chembl.drug_mechanisms.target_components.uniprot"] }'
curl --location --globoff 'https://myvariant.info/v1/query?size=1000&fields=civic.entrez_id,civic.evidence_items&jmespath=civic.evidence_items.disease|[?doid=='DOID:9256']' \ --header 'Content-Type: application/json' \ --data '{ "q": "DOID:9256", "scopes": "civic.evidence_items.disease.doid" }'
My guess is that this error has to do with how these fields are nested (two layers with arrays of objects?)
The text was updated successfully, but these errors were encountered:
Assigning to myself to review and see if this is fixed.
Sorry, something went wrong.
https://suwulab.slack.com/archives/CC19LHAF2/p1713395408672619?thread_ts=1712700743.634569&cid=CC19LHAF2
colleenXu
No branches or pull requests
I get 500 errors when trying to use jmespath for the following queries.
MyChem Query for specific chembl.drug_mechanism gene, trying to keep only matching chembl.drug_mechanism info
GET version
POST version:
Query for specific civic.evidence_items.disease, trying to keep only matching civic.evidence_items info
GET version
POST version:
My guess is that this error has to do with how these fields are nested (two layers with arrays of objects?)
The text was updated successfully, but these errors were encountered: