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

Bug fix #155

Merged
merged 3 commits into from
Jan 21, 2025
Merged

Bug fix #155

merged 3 commits into from
Jan 21, 2025

Conversation

ehwenk
Copy link
Collaborator

@ehwenk ehwenk commented Jan 20, 2025

If there was no data in the excluded_data table, the extract_ functions were returning an empty tibble, not a tibble of empty named, columns. In addition to being the wrong output, this was leading to warnings when running multiple extract_ functions.

A change at the end of the main extract_data function fixes this

fix error - due to excluded_data table being a completely empty tibble rather than having empty columns if there is no excluded_data. Caused a problem with back-to-back extract_ function uses
Forgot I also needed a column "error" and added test.
@ehwenk ehwenk requested a review from dfalster January 20, 2025 21:41
Copy link
Member

@dfalster dfalster left a comment

Choose a reason for hiding this comment

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

Should we also check that excluded data returns an appropriate nibble, even when no data?

In other words, if excluded data has the right format, this problem should never arise. So perhaps need to catch it earlier on, rather than patching it here?

@ehwenk ehwenk merged commit 4437ca3 into develop Jan 21, 2025
10 checks passed
@ehwenk ehwenk deleted the bug-fix branch January 21, 2025 00:00
@ehwenk
Copy link
Collaborator Author

ehwenk commented Jan 21, 2025

Should we also check that excluded data returns an appropriate nibble, even when no data?

In other words, if excluded data has the right format, this problem should never arise. So perhaps need to catch it earlier on, rather than patching it here?

I'm going to look into this. I wanted to merge in the patch for now so that austraits works for others.

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