fix: update Viguno base URL to include /api/v1 to prevent 404 errors #1184
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request fixes the missing
/api/v1segment in the Viguno base URL on the frontend configuration.Currently, frontend requests to Viguno lack the
/api/v1prefix, causing 404 Not Found errors when accessing Viguno endpoints via the proxy.Updating the base URL to include
/api/v1ensures the frontend requests are routed correctly to Viguno's API.Related Issue
Fixes #1182
Motivation and Context
/internal/proxy/viguno/hpo/genes?.../internal/proxy/viguno/api/v1/hpo/genes?.../api/v1return valid data.