Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bug: relative file path for loadquery when ubkg-api endpoints called from hs-ontology-api #119

Closed
AlanSimmons opened this issue Apr 25, 2024 · 0 comments · Fixed by #120
Closed

bug: relative file path for loadquery when ubkg-api endpoints called from hs-ontology-api #119

AlanSimmons opened this issue Apr 25, 2024 · 0 comments · Fixed by #120
Assignees
@AlanSimmons
Labels
bug Something isn't working

Comments

@AlanSimmons
Copy link
Collaborator

Statement of problem

Endpoints in ubkg-api load Cypher query strings from files in a relative file path.

When the hs-ontology-api is the active service, calls to endpoints in ubkg-api are passed through to a library package version of ubkg-api. In these scenarios, the root path is relative to hs-ontology-api, not ubkg-api, making relative paths tricky.

image

Solution

Correct the path assignment in the loadquery utility.
@AlanSimmons AlanSimmons added the bug Something isn't working label Apr 25, 2024
@AlanSimmons AlanSimmons self-assigned this Apr 25, 2024
@AlanSimmons AlanSimmons linked a pull request Apr 25, 2024 that will close this issue
1. Correct relative file location of cypher query strings for scenario when ubkg-api is invoked from hs-ontology-api 2. Fixed issue with minimum depth check in paths/expand call. #120
Merged
@AlanSimmons AlanSimmons moved this from In Progress to Waiting/Blocked in @UBKG (Unified Biomedical Knowledge Graph) Project Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlanSimmons AlanSimmons

Labels
bug Something isn't working
Projects
@UBKG (Unified Biomedical Knowledge Graph) Project
Archived in project
Milestone
No milestone
1 participant
@AlanSimmons