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

Protect against a few null cases #26

Merged
merged 1 commit into from
Mar 22, 2024
Merged

Conversation

OrdiNeu
Copy link
Collaborator

@OrdiNeu OrdiNeu commented Mar 18, 2024

There was only one section left where we weren't checking nullness before using values returned from Katsu -- this fixes that.

@OrdiNeu OrdiNeu requested a review from mshadbolt March 18, 2024 20:44
Copy link
Contributor

@mshadbolt mshadbolt left a comment

Choose a reason for hiding this comment

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

Pulled the branch and did integration tests as well as ingesting new small dataset. Everything worked as expected except that test_query_genomic(), if no results are returned from the search then all donors are displayed in the clinical data. Not sure if this is intentional or we should change it to behave so that if there are no donors matching the genomic search then the table is blank? (probably an issue for another ticket, will approve this change for now)

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.

2 participants