-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
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
Move ARAX to TRAPI 1.1 #1412
Comments
TRAPI 1.1 schemas have been merged into master in the ReasonerAPI repo, so URLs are now: |
TRAPI 1.1 stuff is being set up in the NewFmt branch. |
okay everyone, the pool is open, and let me tell you, changing half your The changes that need to be made are mostly just:
The following are done: and it was a gas! The following need to be done: Note that this will be parallel to our main endpoints for a while. The GUIs are: and the corresponding API endpoints are: The GUI will also need to be updated to speak TRAPI 1.1. It is not yet. Thanks! |
awesome - ok, one issue (unearthed by all of today's work): resultify is complaining about a qnode that has a single curie but has
should |
All the slow tests pass now! |
yes, you're right! I have just checked in a fix I think. |
I have just re-rolled out Thanks everyone! |
awesome! I just tested out having Expand use the v1.1 KG2 endpoint, and all tests (including slow) passed, so I just pushed that to |
excellent! I just rolled out the latest |
ok, I created the |
… cache it in memory so only the first request is slow #1412
outstanding, thanks! Looks great and deployed! Instead of using a browser, y'all may want to test with:
since it's a tad big. |
- new handling and didsplay of node/edge attributes - update stream and cache settings - update DSL and JSON examples - add TRAPI version of message being parsed to status box - minor text edits
TRAPI 1.1-supporting GUI and back-end is deployed to NewFmt (except for Build-A-Graph part) Please test and report. |
when I go to https://arax.ncats.io/kg2NewFmt/, go to the JSON tab, click 'Example', and try to run that query, it gives an error:
should that be working at this point? |
Yes, it should certainly be working. I repro'ed and have now fixed. Please try again. you might need to CTRL+REFRESH to make sure you have the latest JavaScript. I suspect this was a casualty of the ingest of |
nice, looks good now! |
call it done! |
realized we don't seem to have an issue for this yet - creating one so we have a place to document related work
some links from the mini-hackathon we had about this a little ways back:
https://github.com/NCATSTranslator/ReasonerAPI/tree/v1.1.x
https://github.com/NCATSTranslator/ReasonerAPI/blob/v1.1.x/TranslatorReasonerAPI.yaml
https://github.com/NCATSTranslator/ReasonerAPI/blob/v1.1.x/ChangeLog.md
(although it seems these links are now broken?)
The text was updated successfully, but these errors were encountered: