fix(export): In export schema, allow cds name with nuc
prefix, as long as not equal to nuc
#1434
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.
Fixes #1433
Description of proposed changes
Fixes bug #1433 introduced in v23.1.0, that causes validation to fail when gene names start with
nuc
, e.g.nucleocapsid
.Regex excluded all strings that start with
nuc
not justnuc
. Adding a trailing$
to the lookahead fixes that.Checklist
It seems like we don't really test export validation much. I had a look whether I could quickly add a test case for this bug to prevent regression but couldn't see a neat way. I think we should not block this on lacking tests, but rather add an issue to improve testing of validation. Would be nice if there was a way to do more unit tests for export here:
tests/test_validate.py
- and potentially also test validation in an E2E test.