fix: pango lineage filter with null values #403
Merged
Conversation
This file contains 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
JonasKellerer
force-pushed
the
investigateNullPangoLineageFilterValue
branch
from
a27a18c
to
0b604bb
Compare
JonasKellerer
force-pushed
the
investigateNullPangoLineageFilterValue
branch
from
0b604bb
to
35dc0c7
Compare
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.
Summary
In GenSpectrum/LAPIS#760 it was found that filtering for null values does not work correctly. This PR targets this issue. The problem was that null was not allowed for pangolineage filters.
PR Checklist
- [ ] All necessary documentation has been adapted or there is an issue to do so.