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.

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

DSERV-546-variants #89

Merged
merged 9 commits into from
Jul 23, 2024
Merged

DSERV-546-variants #89

merged 9 commits into from
Jul 23, 2024

Conversation

mingjiecn
Copy link
Collaborator

No description provided.

@mingjiecn mingjiecn requested a review from pedrohr July 11, 2024 15:05
Copy link
Contributor

@pedrohr pedrohr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all good! just two items for discussion

]

CATALOG_API_FREQ = 'https://api-dev.catalog.igvf.org/api/variants/freq?page=0&maximum_af=1&limit=500'
CATALOG_API_VARIANTS = 'https://api-dev.catalog.igvf.org/api/variants?page=0&limit=500'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we use production instead? we cant guarantee stability of the api-dev, or make it configurable

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

production API may not satisfy our need. For example right now api/variants/freq endpoint in production can't change limit value. This regulome UI is just a demo for now. I don't think it will be released very soon. I can change the API to production API once it is updated.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good!

notifications[region_query] = 'Failed: invalid region input'
continue
logging.info(f'api: {api}')
res = requests.get(api).json()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this line may raise many exceptions... should we include an error message for backend failure such as "try again soon" for example?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good. Will add it!

@mingjiecn mingjiecn merged commit 72b8fcc into dev Jul 23, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants